Hi Jerome,
Thanks for the update.
One question I had was about the directory structure when it comes to
resources. The standard or preferred Maven structure is
src/main/resources/<appropriate-package>/<resource-files>
I am a bit uncomfortable with this. From what I have seen, developers like
to keep resources that form the strings in (e.g.) exception messages along
side the classes that create them. Thus, we might have:
src/main/java/org/glassfish/util/Util.java
src/main/java/org/glassfish/util/LocalStrings.properties
and then use a LocalStringManager that does the right thing. This can be
achieved by doing:
<build>
<resources>
<resource>
<directory>src/main/java</directory>
</resource>
</resources>
</build>
in pom.xml.
So, my question is should we have that as a practice or should we strive
to do the best practice suggested by Maven?
Regards,
Kedar
Jerome Dochez wrote:
> Hi All
>
> The conversion for subversion is mostly done, you can now checkout and
> build the V3 runtime using the subversion repository.
>
> There are details on how to checkout the entire workspace or individual
> modules in the engineering guide document.
>
> http://wiki.glassfish.java.net/Wiki.jsp?page=V3EngineersGuide#section-V3EngineersGuide-7Building
>
>
> I have also updated all the SCM references from the wiki pages at
> http://wiki.glassfish.java.net/Wiki.jsp?page=PlanForGlassFishV3
>
> let me know if I forgot any or have any questions
>
> Jerome
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>