I'll want to experiment with ways to get combined javadocs out of
these
artifacts (although probably two sets ... I got a suggestion to
split the
APIs that are interesting to application developers from the
"internal" APIs
for those extending the framework, and would like to produce two
sets of
javadocs with their appropriate packages.
Can we do this with custom assemblies?
--
James Mitchell
On Apr 15, 2006, at 11:35 AM, Craig McClanahan wrote:
On 4/15/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 4/14/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
Separately, I'm ready (gulp!) to start moving Shale towards
Maven2, and
it's
recommended soure directory organizations ... as long as you
have-a-clue-about-Maven gurus promise to stand by my side and
help :-).
Of course. :)
I
had a question about the "resources" directories in the organization
recommended by Maven. Does that include resource bundles for
localization
(which are normally placed somewhere in the "src/java" hierarchy
currently),
or is it just for "configuration" files?
Maven's recommended directory structure is src/main/java for .java
files, and src/main/resources for everything else. With that, no
configuration is necessary.
http://maven.apache.org/guides/introduction/introduction-to-the-
standard-directory-layout.html
If you prefer to keep .properties files in with the source code, it
takes some <resource> sections in the pom to get them included in the
jar. Example:
http://svn.apache.org/repos/asf/struts/action/trunk/core/pom.xml
It shouldn't be too hard to remodel the existing organization and
update
the
relevant Ant build.xml files, as a move towards forwards
compatibility
with
the recommended structure.
...
But it makes a lot of sense to
migrate the internal organization of the Shale source
repositories now,
to
make the ultimate conversion easier. Anyone else who wants to
help in
this
is, of course, welcome to have at it.
The major change is splitting core-library into multiple modules,
one per
jar.
Which is the reason I've been resisting so far ... :-)
I'll want to experiment with ways to get combined javadocs out of
these
artifacts (although probably two sets ... I got a suggestion to
split the
APIs that are interesting to application developers from the
"internal" APIs
for those extending the framework, and would like to produce two
sets of
javadocs with their appropriate packages.
Are you planning to keep the Ant build after Maven 2 is in place?
Ideally, no ... it's hard enough to keep one build environment in
sync with
reality. But we'll probably need some user feedback before
decomissioning
the Ant scripts.
--
Wendy
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
