I set up a wiki[1] to record the steps needed. If anyone wants to
move things around feel free. Just be sure to update the wiki so (a)
we know you did it (no emails from the test repos) and (b) we remember
to do it again when its time to reorg for real.
sean
[1]
Quick question. How do you include LICENSE.txt in your jar file.
Isn't it supposed to be automatic if its in your top level dir?
sean
On 12/1/05, Sean Schofield [EMAIL PROTECTED] wrote:
I set up a wiki[1] to record the steps needed. If anyone wants to
move things around feel free. Just be
Sean Schofield wrote:
Quick question. How do you include LICENSE.txt in your jar file.
Isn't it supposed to be automatic if its in your top level dir?
I am not an expert, but my project.xml contains
licenses
license
nameThe Apache Software License, Version 2.0/name
Maybe: http://jira.codehaus.org/browse/MNG-1615
In
maven-jar-plugin/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java
is a @todo Add license files in META-INF directory.
Sean Schofield schrieb:
Quick question. How do you include LICENSE.txt in your jar file.
Isn't it supposed
@ Brend: Thanks for the info.
@ Everyone: I moved all of the resources in the test repository. So
now they are included in the jars.
The only major thing left is transforming and including the TLD's.
Then its on to examples, javadoc and site. So far so good ...
sean
On 12/1/05, Bernd
Keep in mind, that's a Maven 1 site. I haven't quite managed to
convince m2 to do the same thing, but I'm getting closer.
Point taken.
Watch out for http://jira.codehaus.org/browse/MNG-661, m2 will build
the site for each module, but won't aggregate it so you can preview
it.
Yeah I saw
Hello,
I would prefer following approach:
First we should create a 'common' package.
(proposal is done)
Then we move the source to the src/main/java,
src/main/resources and src/test/java folders
and change the ant scripts.
Afterwards we can start creating the pom's.
Until the maven build is
I've created a myfaces project in the *test* SVN repostiory[1]. I've
only included the src files but the resources are also mixed in
there and will need to come out. This is just for test purposes so
that we can tweak the build.
Maybe we should also start a wiki as we move things around so that
If anyone has a Maven2 script in progress for MyFaces I would like to
see it. I'm going to try and start one of my own if nobody produces
one. Since I'm completely new to Maven I will be needing the help of
our Maven experts. Hopefully the Tobago team and Struts lurkers will
be able to help us
I am fairly new to maven, but I could help with that if no one has
already done the script. I am also migrating a private project to
maven, so I am already dealing with this. One question is: it is the
intention to maintain the current structure, or do we adapt the source
tree to the conventions
According to Wendy, its *much* easier to just change the structure to
adopt to Maven. What I would like to do is set up a bunch of SVN
externals to link everything in the manner which Maven expects. This
way we can build nightlies without changing the structure that
everyone else is dealing
I guess that we can configure the pom's in a way that the current
svn:externals remain the same. I think we could only change the
svn:externals for the current folder, having this structure:
current/pom.xml
|
+-- api/pom.xml
|
+-- share/pom.xml (?)
|
+--
On 11/29/05, Sean Schofield [EMAIL PROTECTED] wrote:
According to Wendy, its *much* easier to just change the structure to
adopt to Maven. What I would like to do is set up a bunch of SVN
externals to link everything in the manner which Maven expects. This
way we can build nightlies without
My thinking on the externals was that we create a folder called
myfaces-maven (or something) and have externals that reorg everything
in the way that Maven wants. This wouldn't be a permanent solution,
just a convenient way of building the latest and greatest without
copying everything outright
I agree that we probably will just reorg to comply with Maven (should
we vote to go forward.)
I have a question about Maven website building. It looks like our
subprojects match up pretty nicely with the Maven module concept but
I'm wondering what the final website will look like. Is it
15 matches
Mail list logo
