You need to run "mvn install" to install your plugin into the local repo cache.
Then you can test your plugin in another project by specifying "mvn ...:sayhi".
Wayne
On 8/31/07, siegfried <[EMAIL PROTECTED]> wrote:
> Thanks Wayne, that "-U" appeared to work.
>
> Now I started out the tutorial with the command
> mvn -U archetype:create \
> -DgroupId=sample.plugin \
> -DartifactId=maven-hello-plugin \
> -DarchetypeGroupId=org.apache.maven.archetypes \
> -DarchetypeArtifactId=maven-archetype-mojo
>
> because the tutorial did not tell you where to place the files pom.xml and
> GreetingMojo.java. So I just put GreetingMojo down in the directly with the
> other java source code. Then I clobbered the pom.xml file with pom.xml from
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html.
>
> Below is my pom.xml which I copied from
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html .
> Below that are the results when I try to "mvn
> sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi" as per the
> instructions.
>
> What am I doing wrong? I am not seeing "Hello, World".
>
> I believe I have copied the
> c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/src/main/java/sample/p
> lugin/GreetingMojo.java correctly from that web page.
>
> So then when I realized that I executed the command " mvn -U
> archetype:create... " too soon and tried moving GreetingMojo.java to
> c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/GreetingMojo.java and
> running the command again but that did not help.
>
>
> Thanks,
> Siegfried
>
>
> Here is my c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/pom.xml.
> Does it need to begin with a tag? Why
> not?
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> sample.plugin
> maven-hello-plugin
> maven-plugin
> 1.0-SNAPSHOT
> Sample Parameter-less Maven Plugin
>
>
> org.apache.maven
> maven-plugin-api
> 2.0
>
>
>
>
>
> sample.plugin
> maven-hello-plugin
> 1.0-SNAPSHOT
>
>
>
>
>
> Here are the results:
> cd c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/
> mvn sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi
> [INFO] Scanning for projects...
>
> [INFO] Cannot find mojo descriptor for:
> 'sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi' - Treating as
> non-aggregator.
>
> [INFO]
>
>
> [INFO] Building Sample Parameter-less Maven Plugin
>
> [INFO]task-segment:
> [sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi]
>
> [INFO]
>
>
> [INFO]
>
>
> [ERROR] BUILD FAILURE
>
> [INFO]
>
>
> [INFO] A required plugin was not found: Plugin could not be found - check
> that the goal name is correct: Unable to download the artifact from any
> repository
>
>
>
> Try downloading the file manually from the project website.
>
>
>
> Then, install it using the command:
>
> mvn install:install-file -DgroupId=sample.plugin
> -DartifactId=maven-hello-plugin \
> -Dversion=1.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there: mvn deploy:deploy-file -DgroupId=sample.plugin
> -DartifactId=maven-hello-plugin \
> -Dversion=1.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file
> \
> -Durl=[url] -DrepositoryId=[id]
>
>
>
>
>
> sample.plugin:maven-hello-plugin:maven-plugin:1.0-SNAPSHOT
>
>
>
> from the specified remote repositories:
>
> central (http://repo1.maven.org/maven2)
>
>
>
> sample.plugin:maven-hello-plugin:maven-plugin:1.0-SNAPSHOT
>
>
>
> from the specified remote repositories:
>
> central (http://repo1.maven.org/maven2)
>
>
>
> [INFO]
>
>
> [INFO] For more information, run Maven with the -e switch
>
> [INFO]
>
>
> [INFO] Total time: < 1 second
>
> [INFO] Finished at: Fri Aug 31 00:04:30 MDT 2007
>
> [INFO] Final Memory: 1M/4M
>
> [INFO]
>
>
>
> Compilation exited abnormally with code 1 at Fri Aug 31 00:04:30
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 29, 2007 3:56 PM
> To: Maven Users List
> Subject: Re: Trouble with mojo tutorial
>
> Try mvn -U ... to force an update.
>
> 1.0-alpha-5 was a "failed release". The only available versions are -4 and
> -6.
Thanks Wayne, that "-U" appeared to work.
Now I started out the tutorial with the command
mvn -U archetype:create \
-DgroupId=sample.plugin \
-DartifactId=maven-hello-plugin \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DarchetypeArtifactId=maven-archetype-mojo
because the tutorial did not tell you where to place the files pom.xml and
GreetingMojo.java. So I just put GreetingMojo down in the directly with the
other java source code. Then I clobbered the pom.xml file with pom.xml from
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html.
Below is my pom.xml which I copied from
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html .
Below that are the results when I try to "mvn
sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi" as per the
instructions.
What am I doing wrong? I am not seeing "Hello, World".
I believe I have copied the
c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/src/main/java/sample/p
lugin/GreetingMojo.java correctly from that web page.
So then when I realized that I executed the command " mvn -U
archetype:create... " too soon and tried moving GreetingMojo.java to
c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/GreetingMojo.java and
running the command again but that did not help.
Thanks,
Siegfried
Here is my c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/pom.xml.
Does it need to begin with a tag? Why
not?
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
sample.plugin
maven-hello-plugin
maven-plugin
1.0-SNAPSHOT
Sample Parameter-less Maven Plugin
org.apache.maven
maven-plugin-api
2.0
sample.plugin
maven-hello-plugin
1.0-SNAPSHOT
Here are the results:
cd c:/dev/sandboxes/maven/sample-mojo/maven-hello-plugin/
mvn sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi
[INFO] Scanning for projects...
[INFO] Cannot find mojo descriptor for:
'sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi' - Treating as
non-aggregator.
[INFO]
[INFO] Building Sample Parameter-less Maven Plugin
[INFO]task-segment:
[sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi]
[INFO]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] A required plugin was not found: Plugin could not be found - check
that the goal name is correct: Unable to download the artifact from any
repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=sample.plugin
-DartifactId=maven-hello-plugin \
-Dversion=1.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there: mvn deploy:deploy-file -DgroupId=sample.plugin
-DartifactId=maven-hello-plugin \
-Dversion=1.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file
\
-Durl=[url] -DrepositoryId=[id]
sample.plugin:maven-hello-plugin:maven-plugin:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
sample.plugin:maven-hello-plugin:maven-plugin:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: < 1 second
[INFO] Finished at: Fri Aug 31 00:04:30 MDT 2007
[INFO] Final Memory: 1M/4M
[INFO]
Compilation exited abnormally with code 1 at Fri Aug 31 00:04:30
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 29, 2007 3:56 PM
To: Maven Users List
Subject: Re: Trouble with mojo tutorial
Try mvn -U ... to force an update.
1.0-alpha-5 was a "failed release". The only available versions are -4 and
-6.
Wayne
On 8/29/07, siegfried <[EMAIL PROTECTED]> wrote:
> I'm trying to follow the instructions at
> http://maven.apache.org/guides/plugin/guide-java-plugin-development.html.
> Below are the results.
>
>
>
> Am I experiencing some problem with the public maven repositories or is
this
> a bug in maven 2.0.7? (Or did I do something wrong?)
>
>
>
> What would be the wget command to get maven-archetype-creator:jar as the
> error message suggests?
>
>
>
> Thanks,
>
> Siegfried
>
>
>
>
>
>
>
Hello,
I have a unit test which tests a shell script. This shell script
calls java code, so it fails under Maven, because the java coded
launched by the shell script doesn't have a complete classpath. I can
work around this by using , but it turns out
this was breaking my embedded tomcat.
So I'm wondering, is there any way to export Maven's classworlds
configuration through an environment variable so I can call
System.exec() on some java code and have it work?
If not (and this would actually be preferable), is there any way in
Maven to run tests on an assembly (or other distributable)? If I
could do that, I could write tests and have them test a fully built
distributable, which would let the shell scripts assemble the
classpath the same way we do in production, which would make the test
much more realistic.
Thanks for any suggestions,
Josh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
So you should vote for http://jira.codehaus.org/browse/MECLIPSE-252 too :P
Regards,
Marcin
Dan Tran wrote:
You poms are fine. I have seen this in my projects too.
-D
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
You actually might be able to do this with the remote-resources plugin.
We currently use it to generate the NOTICE files which include the
License for each dependency. Since it's just a velocity template, you
might be able to sort via the licenses before printing anything. Not
really sure though as I'm by no means a velocity expert.
Dan
On Thursday 30 August 2007, Wayne Fay wrote:
> I think a useful license report would simply look at all dependencies
> (including transitive) and then issue a report at the end which simply
> told you:
>
> GPL
> a.b.c-1.0.1
> x.y.z-2.0.2
>
> MIT
> l.m.n-1.0.0-SNAPSHOT
>
> None specified
> f.g.h-4.0.1
>
> You could perhaps go the next step of saying "based on your
> dependencies, it seems like you could use BSD or LGPL" but that would
> require basically hard-coding rules -and- that all of your
> dependencies have licenses declared, which is HIGHLY unlikely.
>
> Wayne
>
> On 8/30/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
> > 'Sure they can, but how do you know if a license is compatible
> > (maybe it should spit out "IANAL" j/k)? Well anyway, I do agree
> > that a license attribute maybe useful none the less.
> >
> > -aps
> >
> > On 8/30/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> > > If the dependencies have maven pom.xml files, they can specify the
> > > license in them.
> > >
> > > Alexander Sack wrote:
> > > > Just out of curiosity, how the heck would you figure this out?
> > > > Seems
> > >
> > > like
> > >
> > > > this would be too complicated to do in software though I AM 100%
> > > > FOR replacing corporate legal teams with a Mojo! :D!
> > > >
> > > > -aps
> > > >
> > > > On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > > >> Not that I know of. If you write it, please contribute it back,
> > > >> perhaps someone else would find it useful.
> > > >>
> > > >> Wayne
> > > >>
> > > >> On 8/30/07, Stephen More <[EMAIL PROTECTED]> wrote:
> > > >>> I would like to release some code as "open source", but I am
> > > >>> not sure which license to pick.
> > > >>>
> > > >>> "Does your project currently use any open source code? If so,
> > > >>> then you may need to use the same license that the open source
> > > >>> code uses, or another license that is compatible with it."
> > > >>>
> > > >>> Maven does a great job with figuring out dependencies. Based
> > > >>> on these dependencies is there a plugin that can identify
> > > >>> what license could be assigned to this project ?
> > > >>>
> > > >>>
> > > >>> -Thanks
> > > >>> Steve More
> > > >>>
> > > >>> --
> > > >>>--- 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]
> > >
> > > --
> > > Dennis Lundberg
> > >
> > > --
> > >--- To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > > additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > "What lies behind us and what lies in front of us is of little
> > concern to what lies within us." -Ralph Waldo Emerson
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Several options... You could attach maven-antrun-plugin and use the
junitreport task directly, if you already have a process that works.
Make sure you include the proper plugin dependency so you have access
to the junitreport task.
Or just call out to your existing build.xml file with ant after
executing Maven to generate the XML files. I've done this in the past
for a deployment to OC4J, after the EAR was generated by Maven.
Or I believe there is an XSLT plugin in the Sandbox that might be helpful.
Wayne
On 8/30/07, Joshua ChaitinPollak <[EMAIL PROTECTED]> wrote:
> Hello,
>
> How can I apply an xslt to our /target/surefire-reports/TEST-*.xml
> files?
>
> In our effort to migrate from ant to maven, I need to apply an xslt
> to our surefire XML reports. This xslt generates an sql file which we
> import into a database to track our continuous integration status
> over time.
>
> Currently this is managed by the target in ant.
>
> Thanks,
>
> Josh
>
> --
> Joshua ChaitinPollak
> Software Engineer
> Kiva Systems
>
>
>
> -
> 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]
Meiko,
I'm surprised you are getting any resources copied during your build,
you seem to be excluding them all:
**/*
What resource file is being copied without filtering being applied?
And what does your filter file look like?
William
-Original Message-
From: meiko [mailto:[EMAIL PROTECTED]
Sent: Friday, 31 August 2007 9:01 AM
To: users@maven.apache.org
Subject: [***POSSIBLE SPAM***] - filtering properties like pom.* dont
work - Email has different SMTP TO: and MIME TO: fields in the email
addresses
I have a problem with filtering.
- properties like maven.* or pom.* or project.*(e.g. ${pom.version})
dont work
- other properties like ${basedir} or ${java.version} work What could be
the reason ?
Thank you for helping a frustrated maven-user ;-)
here is my pom:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
trilobita-game
trilobita
1.0
4.0.0
trilobita
trilobita-frontend
war
1.0
${basedir}/src/main/resources/components.properties
/src/main/resources/
**/*
maven-compiler-plugin
1.5
1.5
maven-war-plugin
2.0
${basedir}/src/main/webapp
true
jboss
jboss-seam-ui
1.2.1.GA
--
View this message in context:
http://www.nabble.com/filtering-properties-like-pom.*-dont-work-tf435738
4s177.html#a12417818
Sent from the Maven - Users mailing list archive at Nabble.com.
-
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]
I thought a plugin for this might be asking for too much, but what
about the possibility of modifying the Dependencies report from the
site to include a license column ?
The output could look something like this:
http://jspwiki.org/wiki/ApacheRelicensing
-Steve
On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I think a useful license report would simply look at all dependencies
> (including transitive) and then issue a report at the end which simply
> told you:
>
> GPL
> a.b.c-1.0.1
> x.y.z-2.0.2
>
> MIT
> l.m.n-1.0.0-SNAPSHOT
>
> None specified
> f.g.h-4.0.1
>
> You could perhaps go the next step of saying "based on your
> dependencies, it seems like you could use BSD or LGPL" but that would
> require basically hard-coding rules -and- that all of your
> dependencies have licenses declared, which is HIGHLY unlikely.
>
> Wayne
>
> On 8/30/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
> > 'Sure they can, but how do you know if a license is compatible (maybe it
> > should spit out "IANAL" j/k)? Well anyway, I do agree that a license
> > attribute maybe useful none the less.
> >
> > -aps
> >
> > On 8/30/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> > >
> > > If the dependencies have maven pom.xml files, they can specify the
> > > license in them.
> > >
> > > Alexander Sack wrote:
> > > > Just out of curiosity, how the heck would you figure this out? Seems
> > > like
> > > > this would be too complicated to do in software though I AM 100% FOR
> > > > replacing corporate legal teams with a Mojo! :D!
> > > >
> > > > -aps
> > > >
> > > > On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > > >> Not that I know of. If you write it, please contribute it back,
> > > >> perhaps someone else would find it useful.
> > > >>
> > > >> Wayne
> > > >>
> > > >> On 8/30/07, Stephen More <[EMAIL PROTECTED]> wrote:
> > > >>> I would like to release some code as "open source", but I am not sure
> > > >>> which license to pick.
> > > >>>
> > > >>> "Does your project currently use any open source code? If so, then you
> > > >>> may need to use the same license that the open source code uses, or
> > > >>> another license that is compatible with it."
> > > >>>
> > > >>> Maven does a great job with figuring out dependencies. Based on these
> > > >>> dependencies is there a plugin that can identify what license could
> > > >>> be assigned to this project ?
> > > >>>
> > > >>>
> > > >>> -Thanks
> > > >>> Steve More
> > > >>>
> > > >>> -
> > > >>> 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]
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> > > --
> > > Dennis Lundberg
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > "What lies behind us and what lies in front of us is of little concern to
> > what lies within us." -Ralph Waldo Emerson
> >
>
> -
> 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]
Finally got it fixed...after alot of research...it was due to a maven (2.0.7)
issue on windows...issue - MNG-3084...had to modify the mvn.bat file to get
it working.
Thanks nyways
Farhan.
mfs wrote:
>
> Dear All,
>
> I am getting this strange behavior where even on a build-failure (as
> below) as shown in the Result, the success icon is shown against the
> project on "show-project" screen and same is the case with history screen
> against a project...and even no emails are sent as its intrepreting that
> the build is a success (dont know why) and no state change since last
> build..
>
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Share : PDFP
> [INFO]task-segment: [clean, install]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target\classes
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target\test-classes
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target\site
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Compiling 18 source files to
> C:\continuum\continuum_wd\8\target\classes
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
> C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1,0]
> 'class' or 'interface' expected
>
>
>
> C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1,0]
> 'class' or 'interface' expected
>
>
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Aug 30 11:01:50 PDT 2007
> [INFO] Final Memory: 4M/8M
> [INFO]
>
>
>
--
View this message in context:
http://www.nabble.com/Strange---Success-icon-shown-and-no-emails-sent-in-case-of-build-failure-tf4355976.html#a12417831
Sent from the Continuum - Users mailing list archive at Nabble.com.
I have a problem with filtering.
- properties like maven.* or pom.* or project.*(e.g. ${pom.version}) dont
work
- other properties like ${basedir} or ${java.version} work
What could be the reason ?
Thank you for helping a frustrated maven-user ;-)
here is my pom:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
trilobita-game
trilobita
1.0
4.0.0
trilobita
trilobita-frontend
war
1.0
${basedir}/src/main/resources/components.properties
/src/main/resources/
**/*
maven-compiler-plugin
1.5
1.5
maven-war-plugin
2.0
${basedir}/src/main/webapp
true
jboss
jboss-seam-ui
1.2.1.GA
--
View this message in context:
http://www.nabble.com/filtering-properties-like-pom.*-dont-work-tf4357384s177.html#a12417818
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks !! That worked :)
On 8/25/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> It's possible but you have to :
> - add a junit 4.x dependency in your project
> For exemple :
>
> junit
> junit
> 4.1
> jar
>
> - add an adapter in your tests :
> /**
> * @return instance of this as Junit test case
> */
> public static junit.framework.Test suite ()
> {
> return new JUnit4TestAdapter(IntTestSpringCoherency.class);
> }
>
> http://jira.codehaus.org/browse/MPTEST-65
>
> Arnaud
>
> On 24/08/07, Manali Joshi <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > I want to include Junit4 unit tests for my project which uses maven 1.1.
> >
> > Currently, I am getting test failures when I try to run those with the
> > following failure error -
> >
> > Testsuite: com.HibernateMappingsTest
> > Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.328 sec
> >
> > Testcase: warning(junit.framework.TestSuite$1):FAILED
> > No tests found in com.HibernateMappingsTest
> > junit.framework.AssertionFailedError: No tests found in
> > com.HibernateMappingsTest
> >
> > My project.xml includes the following plugin -
> > maven-junit-report-plugin
> >
> >
> > Is it possible to run junit4 tests in maven 1.1 ? If so, what plugin do
> I
> > need to use or what configuration am I missing ? Please help..
> >
> > thanks,
> > manali
> >
>
>
> --
> ..
> Arnaud HERITIER
> ..
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
thanks, it works that way. You need to specify everything to work.
Previously I did try using "mvn ant:2.0-beta-2-SNAPSHOT:ant"
(partial-artifact-id:version:goal) thinking that it would determine the
groupId and artifactId somehow if they are missing or partially
specified from the command much like when you just do "mvn ant:ant" that
is getting the latest plugin in the central repo, but it did not work
and made me think there is no other way from command line.
regards,
Srinivasan Chikkala
Open ESB Community (http://open-esb.org)
Wayne Fay wrote:
Yes, that is exactly correct:
mvn groupId:artifactId:version:goal
Wayne
On 8/30/07, Srinivasan Chikkala <[EMAIL PROTECTED]> wrote:
Thanks for the info. I fixed this part by removing the apache maven
repository from the mirror and adding it as a repository ( I just copied
the apache profile specified at
http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
) to my settings.xml. However, when I run "mvn ant:ant" it still picking
up the "2.0-beta-1" from the central repository. So, I added the plugin
configuration ( under ) explicitly in my project pom file to
pick up the "2.0-beta-1-SNAPSHOT" and it downloaded and used that
version, but got the exception using it.
Another question is that if I don't want to configured the plugin in the
project pom for a particular version of a plugin, what are my other
options? Is the plugin registry the only option to force the mvn to use
particular version of the plugin? how can I tell maven to use a
particular version of the plugin using command line options when I am
calling the plugin goal directly from command line ( for example like
"mvn :::goal" )?
BTW, the exception I got from using 2.0-beta-1-SNAPSHOT or 2.0-SNAPSHOT is
java.lang.ClassCastException: java.util.HashMap
at
org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenPluginOptions(AntBuildWriterUtil.java:980)
at
org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenCompilerPluginOptions(AntBuildWriterUtil.java:778)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTasks(AntBuildWriter.java:964)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTarget(AntBuildWriter.java:652)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:280)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:112)
at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
regards,
Srinivasan Chikkala
Open ESB Community (http://open-esb.org)
Tim Kettler wrote:
Hi,
I can't say if this is the final root of your problem but you should
start by fixing the repository definitions in your settings.xml and
see if that helps:
Srinivasan Chikkala schrieb:
Any help on how to get the latest maven-ant-plugin (
maven-ant-plugin-2.0-SNAPSHOT.jar) ?
I am trying to use the latest maven-ant-plugin, but when I execute
"mvn ant:ant" after setting the settings.xml entry
repo1
http://repo1.maven.org/maven2
central
'http://repo1.maven.org/maven2' *is* the URL of central, so you are
effectivly mirroring central with itself. You can savely just leave
that definition out.
snapshot.apache.org
http://people.apache.org/maven-snapshot-repository
central
'http://people.apache.org/maven-snapshot-repository' *is not* a mirror
of central. It contains just the snapshot releases of ASF artifacts.
This should just be a regular repository definition in your settings [1].
-Tim
[1]
http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
[...]
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Joshua ChaitinPollak wrote:
If not (and this would actually be preferable), is there any way in
Maven to run tests on an assembly (or other distributable)? If I could
do that, I could write tests and have them test a fully built
distributable, which would let the shell scripts assemble the classpath
the same way we do in production, which would make the test much more
realistic.
In our case we try and avoid classpath hell as much as we can by
creating uberjars of all our executable code. Uberjars are self
contained jars with all dependencies included, we don't need to worry
about classpaths anywhere.
We use the assembly plugin to create a jar-with-dependencies uberjar to
do this.
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Signature
Hello,
I have a unit test which tests a shell script. This shell script
calls java code, so it fails under Maven, because the java coded
launched by the shell script doesn't have a complete classpath. I can
work around this by using , but it turns out
this was breaking my embedded tomcat.
So I'm wondering, is there any way to export Maven's classworlds
configuration through an environment variable so I can call
System.exec() on some java code and have it work?
If not (and this would actually be preferable), is there any way in
Maven to run tests on an assembly (or other distributable)? If I
could do that, I could write tests and have them test a fully built
distributable, which would let the shell scripts assemble the
classpath the same way we do in production, which would make the test
much more realistic.
Thanks for any suggestions,
Josh
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 8/30/07, Alan D. Salewski <[EMAIL PROTECTED]> wrote:
>
> Hope that cookbook is helpful to someone,
This is a great contribution. I don't suppose I could get you to post
it in the Maven User Wiki?
http://docs.codehaus.org/display/MAVENUSER/Home
Wayne
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, Aug 17, 2007 at 10:35:19AM -0400, Alan D. Salewski spake thus:
> On Fri, Aug 17, 2007 at 09:19:12AM -0500, Wayne Fay spake thus:
> > I don't use the SAR plugin but I think I understand the error
> > message... It looks like your dependencies define the sar as
> > jboss-sar without a classifier... and then your EAR
> > configuration says jboss-sar without a packaging.
> >
> > I'd assume one of those is wrong. My guess would be to change
> > to .
> >
> > Wayne
> [...]
>
> My recent experience with the jboss-packaging-maven-plugin confirms
> Wayne's suspicion. In my particular case, simply omitting the
> 'classfier' element from the EJB solved the problem.
>
> >
> > On 8/16/07, Steve Dobson <[EMAIL PROTECTED]> wrote:
> [...]
> > > However it builds just fine if I remove the SAR information. What am I
> > > doing wrong?
> [...]
> > >
> > >uk.org.syscall.pugwash
> > >pugwash-sar
> > >2.0
> > >jboss-sar
> > >
> [...]
>
> That's fine as is.
>
> > >
> > > uk.org.syscall.pugwash
> > > pugwash-sar
> > > jboss-sar
> > >
>
> Try this, instead:
>
>
> uk.org.syscall.pugwash
> pugwash-sar
>
>
> HTH,
> -Al
[ Since I found myself again working with SAR files, and my earlier post
turned out to be antihelp to myself (and I hope not too many others), I
think it's only appropriate that I reply to my own busted post to set
the record straight... ]
First, for the untainted, there are currently several different
maven-2.x plugins that purport to produce SAR files (JBoss-specific
"Service ARchives"). My comments below below pertain only to use of the
'jboss-packaging-maven-plugin' plugin, currently available in the
codehaus.org snapshots repository:
http://snapshots.repository.codehaus.org/org/codehaus/mojo/jboss-packaging-maven-plugin/
To configure use of the plugin, I added the following snippets to my
top-level pom.xml file:
myproj-sar
myproj-ear
...
...
...
${project.groupId}
myproj-sar
${project.version}
sar
...
...
...
...
org.apache.maven.plugins
maven-ear-plugin
2.3.1
org.codehaus.mojo
jboss-packaging-maven-plugin
2.0-SNAPSHOT
...
...
org.codehaus.mojo
jboss-packaging-maven-plugin
true
...
...
...
In the pom.xml of the subproject that produces the SAR file, I declared
the packaging type as 'jboss-sar':
...
myproj-sar
jboss-sar
...
Note that the dependencyManagement entry for the SAR subproject in the
top-level pom.xml indicates type 'sar', but the packaging type declared
by the SAR subproject itself is 'jboss-sar'. During the 'install' build
phase, the SAR subproject will install the artifact with a '.sar'
extension in the local maven repository.
In the pom.xml of the subproject that produces the EAR file, I have the
following relevant snippets:
...
...
${project.groupId}
myproj-sar
sar
...
...
org.apache.maven.plugins
maven-ear-plugin
5
...
${project.groupId}
myproj-sar
...
...
package
ear
The things to note about this snippet are that the dependency type of
the SAR module is 'sar' (not 'jboss-sar'), and the 'SarModule' element
of the maven-ear-plugin configuration does not include a classifier.
Hope that cookbook is helpful to someone,
-Al
--
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
::
Alan D. Salewski
Software Developer
Health Market Science, Inc.
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
::
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Below is the stack-trace from the continuum log...i just tried uploading the
pom this time instead of providing the pom url...but still the same issue..
179243 [pool-2-thread-1] INFO
org.apache.maven.continuum.scm.ContinuumScm:default - Checking out project:
'Share : PDFP', id: '6' to
'C:\appl\continuum-1.1-beta-2\apps\continuum\webapp\WEB-INF\working-directory\6'.
179296 [pool-2-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default - Executing: cmd.exe /X /C
'"svn --non-interactive checkout http://localhost/svn/repos/pdfp 6"'
179296 [pool-2-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default - Working directory:
C:\appl\continuum-1.1-beta-2\apps\continuum\webapp\WEB-INF\working-directory
180009 [pool-2-thread-1] INFO
org.apache.maven.continuum.scm.ContinuumScm:default - Checked out 23 files.
190923 [SocketListener0-0] INFO
org.apache.maven.continuum.Continuum:default - Enqueuing 'Share : PDFP'
(Build definition id=6).
190933 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Initializing build
190945 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Starting build of Share : PDFP
190992 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Updating working dir
190993 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Performing action check-working-directory
190996 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Performing action update-working-directory-from-scm
191015 [pool-1-thread-1] INFO
org.apache.maven.continuum.scm.ContinuumScm:default - Updating project: id:
'6', name 'Share : PDFP'.
191046 [pool-1-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default - Executing: cmd.exe /X /C
'"svn --non-interactive update"'
191046 [pool-1-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default - Working directory:
C:\appl\continuum-1.1-beta-2\apps\continuum\webapp\WEB-INF\working-directory\6
192035 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Merging SCM results
192035 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Changes found, building
192035 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Performing action update-project-from-working-directory
192041 [pool-1-thread-1] INFO
org.codehaus.plexus.action.Action:update-project-from-working-directory -
Updating project 'Share : PDFP' from checkout.
192184 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Performing action execute-builder
192276 [pool-1-thread-1] INFO
org.apache.maven.continuum.utils.shell.ShellCommandHelper:default -
Executing: cmd.exe /X /C '"C:\appl\maven-2.0.7\bin\mvn --batch-mode
--non-recursive -Dcontinuum.project.lastBuild.state=10
-Dcontinuum.project.nextBuild.number=1 "-Dcontinuum.project.group.name=Share
: PDFP" -Dcontinuum.project.lastBuild.number=0 clean install"'
192277 [pool-1-thread-1] INFO
org.apache.maven.continuum.utils.shell.ShellCommandHelper:default - Working
directory:
C:\appl\continuum-1.1-beta-2\apps\continuum\webapp\WEB-INF\working-directory\6
194410 [pool-1-thread-1] INFO
org.apache.maven.continuum.execution.ContinuumBuildExecutor:maven2 - Exit
code: 0
194527 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default -
Performing action deploy-artifact
195015 [pool-1-thread-1] INFO
org.codehaus.plexus.notification.notifier.Notifier:mail - Sending message:
>From '"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>'.
195016 [pool-1-thread-1] INFO
org.codehaus.plexus.notification.notifier.Notifier:mail - Recipient: To
'<[EMAIL PROTECTED]>'.
639714 [SocketListener0-0] INFO
org.apache.maven.continuum.build.settings.SchedulesActivator:default -
Unactivating schedule DEFAULT_SCHEDULE
639714 [SocketListener0-0] INFO
org.apache.maven.continuum.build.settings.SchedulesActivator:default -
Stopping active schedule "DEFAULT_SCHEDULE".
639714 [SocketListener0-0] INFO
org.apache.maven.continuum.build.settings.SchedulesActivator:default -
Activating schedule DEFAULT_SCHEDULE
639715 [SocketListener0-0] INFO
org.apache.maven.continuum.build.settings.SchedulesActivator:default -
DEFAULT_SCHEDULE: next fire time ->Thu Aug 30 14:25:00 PDT 2007
665793 [SocketListener0-1] INFO
com.opensymphony.xwork.interceptor.Interceptor:exceptionLogging - Error
ocurred during execution
java.io.FileNotFoundException: 6\pom.xml (The system cannot find the path
specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at java.io.FileReader.(FileReader.java:55)
at
org.apache.maven.continuum.web.action.ReleasePrepareAction.getReleasePluginParameters(ReleasePrepareAction.java:128)
a
Yes, that is exactly correct:
mvn groupId:artifactId:version:goal
Wayne
On 8/30/07, Srinivasan Chikkala <[EMAIL PROTECTED]> wrote:
>
> Thanks for the info. I fixed this part by removing the apache maven
> repository from the mirror and adding it as a repository ( I just copied
> the apache profile specified at
> http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
> ) to my settings.xml. However, when I run "mvn ant:ant" it still picking
> up the "2.0-beta-1" from the central repository. So, I added the plugin
> configuration ( under ) explicitly in my project pom file to
> pick up the "2.0-beta-1-SNAPSHOT" and it downloaded and used that
> version, but got the exception using it.
>
> Another question is that if I don't want to configured the plugin in the
> project pom for a particular version of a plugin, what are my other
> options? Is the plugin registry the only option to force the mvn to use
> particular version of the plugin? how can I tell maven to use a
> particular version of the plugin using command line options when I am
> calling the plugin goal directly from command line ( for example like
> "mvn :::goal" )?
>
> BTW, the exception I got from using 2.0-beta-1-SNAPSHOT or 2.0-SNAPSHOT is
>
> java.lang.ClassCastException: java.util.HashMap
> at
> org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenPluginOptions(AntBuildWriterUtil.java:980)
> at
> org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenCompilerPluginOptions(AntBuildWriterUtil.java:778)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTasks(AntBuildWriter.java:964)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTarget(AntBuildWriter.java:652)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:280)
> at
> org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:112)
> at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>
> regards,
>
> Srinivasan Chikkala
> Open ESB Community (http://open-esb.org)
>
>
>
> Tim Kettler wrote:
> > Hi,
> >
> > I can't say if this is the final root of your problem but you should
> > start by fixing the repository definitions in your settings.xml and
> > see if that helps:
> >
> > Srinivasan Chikkala schrieb:
> >>
> >> Any help on how to get the latest maven-ant-plugin (
> >> maven-ant-plugin-2.0-SNAPSHOT.jar) ?
> >>
> >> I am trying to use the latest maven-ant-plugin, but when I execute
> >> "mvn ant:ant" after setting the settings.xml entry
> >>repo1
> >>http://repo1.maven.org/maven2
> >>central
> >>
> >
> > 'http://repo1.maven.org/maven2' *is* the URL of central, so you are
> > effectivly mirroring central with itself. You can savely just leave
> > that definition out.
> >
> >>
> >>snapshot.apache.org
> >>http://people.apache.org/maven-snapshot-repository
> >>central
> >>
> >
> > 'http://people.apache.org/maven-snapshot-repository' *is not* a mirror
> > of central. It contains just the snapshot releases of ASF artifacts.
> > This should just be a regular repository definition in your settings [1].
> >
> > -Tim
> >
> > [1]
> >
> http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
> >
> >
> > [...]
> >
> > -
> > 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]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
If I understood this correctly, you are trying to add a ".xyz" file in
your archetype. If that is correct, yes, you can add these files also in
the archetype. Just add them to the "archetype-resources" directory the
same way you add the other source or template files and update your
META-INF/maven/archetype.xml to include them in the resources. For
example, see the attached .project and .class file that I used for my
archetype that creates a maven project which also can be opened as a
pure eclipse project. I have used the "artifactId" variable in the
.project to specify the eclipse project display name.
META-INF/maven/archetype.xml
...
.project
.classpath
regards,
Srinivasan Chikkala
Open ESB Community (http://open-esb.org)
Mick Knutson wrote:
I want to know if it is possible to have and configure .project and
.classpath files for eclipse in my archetype?
JBI Binding Component[${artifactId}]
org.eclipse.jdt.core.javabuilder
org.eclipse.jdt.core.javanature
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
P.S. I'm using the latests releases: Archiva 1.0-beta-1 and Continuum
1.1-beta-2.
On 8/30/07, Hilco Wijbenga <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm trying to set up both Archiva and Continuum on the same box. I
> would like to have them run in the same Plexus instance and on the
> same port number but that seems too complicated to accomplish (for me
> :-) ).
>
> I found an email by Arnaud Bailly ("Continuum+archiva in same
> application") but the information seems out of date.
>
> Giving up on one Plexus instance and a single port number ... how
> about sharing the user database?
>
> I changed the database location in plexus.conf (both in Archiva and
> Continuum) and now both Continuum and Archiva use the same database
> ... but apparently not at the same time. I can run either Archiva *or*
> Continuum but not both. The app that gets started last fails to
> connect to the user database.
>
> I had a look on the Plexus site to see if I could find anything there
> (I assume I have to configure Plexus somehow to get this to work) but
> no luck.
>
> Would anyone be able to shed some light on this and/or point me in the
> right direction?
>
> Cheers,
> Hilco
>
Hi all,
I'm trying to set up both Archiva and Continuum on the same box. I
would like to have them run in the same Plexus instance and on the
same port number but that seems too complicated to accomplish (for me
:-) ).
I found an email by Arnaud Bailly ("Continuum+archiva in same
application") but the information seems out of date.
Giving up on one Plexus instance and a single port number ... how
about sharing the user database?
I changed the database location in plexus.conf (both in Archiva and
Continuum) and now both Continuum and Archiva use the same database
... but apparently not at the same time. I can run either Archiva *or*
Continuum but not both. The app that gets started last fails to
connect to the user database.
I had a look on the Plexus site to see if I could find anything there
(I assume I have to configure Plexus somehow to get this to work) but
no luck.
Would anyone be able to shed some light on this and/or point me in the
right direction?
Cheers,
Hilco
Another possibility is that the documentation is merely incorrect (or
forward-looking ie "at some point this is what will be possible") or
your interpretation of what "layered archetype" means is incorrect.
I'm not sure what the correct answer is here, because I like
constructing my pom.xml files manually, so I've never been interested
in this feature as yet.
Wayne
On 8/30/07, Andrew Leer <[EMAIL PROTECTED]> wrote:
> Yeah its definitely Friday, I know that feeling...but I do not think
> you are dumb, if you don't understand what I am saying, I am just not
> communicating clearly enough:
>
> The resulting pom.xml file I get after running "mvn archetype:create"
> using the two aforementioned archetypes I mentioned above, in this
> order:
>
> 1. Java6Archetype
> 2. JUnit4Archetype
>
> As you can bellow the resulting pom.xml file in the Layered Test
> project only matches that of the Java6Archetype, as the
> JUnit4Archetype dependencies are not included in the pom.xml file.
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.mooo
> LayeredTestArtifact
> 1.0-SNAPSHOT
>
>
>
>org.apache.maven.plugins
>maven-compiler-plugin
>
>1.5
>1.5
>
>
>
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
>
>
>leeand00
>Andrew J. Leer
>[EMAIL PROTECTED]
>http://www.facebook.com/p/Andrew_J_Leer/698010716
>
>
>
> Resulting pom.xml file after running "mvn archetype:create" twice
> on the same project, using two different Archetypes.
>
> -
> 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]
Hello,
I have a profiles.xml that has 2 profiles within it. The default
profile is set to be active by default, which works fine. I then would
like to activate more profiles based on an environment variable
'DEV_USER'. Within my pom.xml, I can access 'DEV_USER' successfully by
doing the following "${env.DEV_USER}". Unfortuately, when I try to
access that same variable within my 'profiles.xml', it's not recognized,
preventing that profile from activating. I have tried naming that
property DEV_USER, ${DEV_USER}, env.DEV_USER, and ${env.DEV_USER}, none
of which were a success. However, if I run "mvn help:active-profiles
-DDEV_USER" from a commandline, both profiles are activated, which is
what I want.
Is it not possible to access system variables from within a
profiles.xml?
Thanks for any clarification,
Kevin
Profiles.xml
default
true
bert
false
DEV_USER
Hi,
periodically I have to upload a new version of a third-party library to
a private repository using following command:
mvn deploy:deploy-file -Durl= -DrepositoryId= -Dfile= -DpomFile=
This override the current associated maven-metadata.xml file.
Is there a way to only update this file? I would like to keep at least
the /versioning/latest information.
Thanks,
Julien
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yeah its definitely Friday, I know that feeling...but I do not think
you are dumb, if you don't understand what I am saying, I am just not
communicating clearly enough:
The resulting pom.xml file I get after running "mvn archetype:create"
using the two aforementioned archetypes I mentioned above, in this
order:
1. Java6Archetype
2. JUnit4Archetype
As you can bellow the resulting pom.xml file in the Layered Test
project only matches that of the Java6Archetype, as the
JUnit4Archetype dependencies are not included in the pom.xml file.
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.mooo
LayeredTestArtifact
1.0-SNAPSHOT
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
junit
junit
3.8.1
test
leeand00
Andrew J. Leer
[EMAIL PROTECTED]
http://www.facebook.com/p/Andrew_J_Leer/698010716
Resulting pom.xml file after running "mvn archetype:create" twice
on the same project, using two different Archetypes.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I want to know if it is possible to have and configure .project and
.classpath files for eclipse in my archetype?
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
We have just upgraded to the latest version of Archiva and I have a
couple of security questions.
1. In the previous release we added our archiva repository to our
~/.m2/settings.xml as a mirror.
...
catchy
EBS Maven Repository Manager
http:///archiva/repository/internal
central
...
That way when you ran a mvn command it would try to download the plug-
in or resource from our archiva repository and proxy to the central
if needed. We were adding the guest account to the repository-
observer role, but we would like to stop doing that and make users
authenticate to use our archiva repository. What is the proper way
to set that up, so that when mvn runs it can still download from
archiva? It doesn't seem like the repository or mirror configuration
in the settings.xml allow you to setup a username/password, so I'm
not sure how this should be done.
2. Is there anyway to setup archiva to authenticate against an LDAP
directory, rather than the builit-in authentication scheme?
Thanks,
Joel Morris
I think a useful license report would simply look at all dependencies
(including transitive) and then issue a report at the end which simply
told you:
GPL
a.b.c-1.0.1
x.y.z-2.0.2
MIT
l.m.n-1.0.0-SNAPSHOT
None specified
f.g.h-4.0.1
You could perhaps go the next step of saying "based on your
dependencies, it seems like you could use BSD or LGPL" but that would
require basically hard-coding rules -and- that all of your
dependencies have licenses declared, which is HIGHLY unlikely.
Wayne
On 8/30/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
> 'Sure they can, but how do you know if a license is compatible (maybe it
> should spit out "IANAL" j/k)? Well anyway, I do agree that a license
> attribute maybe useful none the less.
>
> -aps
>
> On 8/30/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >
> > If the dependencies have maven pom.xml files, they can specify the
> > license in them.
> >
> > Alexander Sack wrote:
> > > Just out of curiosity, how the heck would you figure this out? Seems
> > like
> > > this would be too complicated to do in software though I AM 100% FOR
> > > replacing corporate legal teams with a Mojo! :D!
> > >
> > > -aps
> > >
> > > On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > >> Not that I know of. If you write it, please contribute it back,
> > >> perhaps someone else would find it useful.
> > >>
> > >> Wayne
> > >>
> > >> On 8/30/07, Stephen More <[EMAIL PROTECTED]> wrote:
> > >>> I would like to release some code as "open source", but I am not sure
> > >>> which license to pick.
> > >>>
> > >>> "Does your project currently use any open source code? If so, then you
> > >>> may need to use the same license that the open source code uses, or
> > >>> another license that is compatible with it."
> > >>>
> > >>> Maven does a great job with figuring out dependencies. Based on these
> > >>> dependencies is there a plugin that can identify what license could
> > >>> be assigned to this project ?
> > >>>
> > >>>
> > >>> -Thanks
> > >>> Steve More
> > >>>
> > >>> -
> > >>> 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]
> > >>
> > >>
> > >
> > >
> >
> >
> > --
> > Dennis Lundberg
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> "What lies behind us and what lies in front of us is of little concern to
> what lies within us." -Ralph Waldo Emerson
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
'Sure they can, but how do you know if a license is compatible (maybe it
should spit out "IANAL" j/k)? Well anyway, I do agree that a license
attribute maybe useful none the less.
-aps
On 8/30/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
>
> If the dependencies have maven pom.xml files, they can specify the
> license in them.
>
> Alexander Sack wrote:
> > Just out of curiosity, how the heck would you figure this out? Seems
> like
> > this would be too complicated to do in software though I AM 100% FOR
> > replacing corporate legal teams with a Mojo! :D!
> >
> > -aps
> >
> > On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> >> Not that I know of. If you write it, please contribute it back,
> >> perhaps someone else would find it useful.
> >>
> >> Wayne
> >>
> >> On 8/30/07, Stephen More <[EMAIL PROTECTED]> wrote:
> >>> I would like to release some code as "open source", but I am not sure
> >>> which license to pick.
> >>>
> >>> "Does your project currently use any open source code? If so, then you
> >>> may need to use the same license that the open source code uses, or
> >>> another license that is compatible with it."
> >>>
> >>> Maven does a great job with figuring out dependencies. Based on these
> >>> dependencies is there a plugin that can identify what license could
> >>> be assigned to this project ?
> >>>
> >>>
> >>> -Thanks
> >>> Steve More
> >>>
> >>> -
> >>> 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]
> >>
> >>
> >
> >
>
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson
Thanks for the info. I fixed this part by removing the apache maven
repository from the mirror and adding it as a repository ( I just copied
the apache profile specified at
http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
) to my settings.xml. However, when I run "mvn ant:ant" it still picking
up the "2.0-beta-1" from the central repository. So, I added the plugin
configuration ( under ) explicitly in my project pom file to
pick up the "2.0-beta-1-SNAPSHOT" and it downloaded and used that
version, but got the exception using it.
Another question is that if I don't want to configured the plugin in the
project pom for a particular version of a plugin, what are my other
options? Is the plugin registry the only option to force the mvn to use
particular version of the plugin? how can I tell maven to use a
particular version of the plugin using command line options when I am
calling the plugin goal directly from command line ( for example like
"mvn :::goal" )?
BTW, the exception I got from using 2.0-beta-1-SNAPSHOT or 2.0-SNAPSHOT is
java.lang.ClassCastException: java.util.HashMap
at
org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenPluginOptions(AntBuildWriterUtil.java:980)
at
org.apache.maven.plugin.ant.AntBuildWriterUtil.getMavenCompilerPluginOptions(AntBuildWriterUtil.java:778)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTasks(AntBuildWriter.java:964)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeCompileTarget(AntBuildWriter.java:652)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeGeneratedBuildXml(AntBuildWriter.java:280)
at
org.apache.maven.plugin.ant.AntBuildWriter.writeBuildXmls(AntBuildWriter.java:112)
at org.apache.maven.plugin.ant.AntMojo.execute(AntMojo.java:112)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
regards,
Srinivasan Chikkala
Open ESB Community (http://open-esb.org)
Tim Kettler wrote:
Hi,
I can't say if this is the final root of your problem but you should
start by fixing the repository definitions in your settings.xml and
see if that helps:
Srinivasan Chikkala schrieb:
Any help on how to get the latest maven-ant-plugin (
maven-ant-plugin-2.0-SNAPSHOT.jar) ?
I am trying to use the latest maven-ant-plugin, but when I execute
"mvn ant:ant" after setting the settings.xml entry
repo1
http://repo1.maven.org/maven2
central
'http://repo1.maven.org/maven2' *is* the URL of central, so you are
effectivly mirroring central with itself. You can savely just leave
that definition out.
snapshot.apache.org
http://people.apache.org/maven-snapshot-repository
central
'http://people.apache.org/maven-snapshot-repository' *is not* a mirror
of central. It contains just the snapshot releases of ASF artifacts.
This should just be a regular repository definition in your settings [1].
-Tim
[1]
http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
[...]
-
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]
If the dependencies have maven pom.xml files, they can specify the
license in them.
Alexander Sack wrote:
Just out of curiosity, how the heck would you figure this out? Seems like
this would be too complicated to do in software though I AM 100% FOR
replacing corporate legal teams with a Mojo! :D!
-aps
On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
Not that I know of. If you write it, please contribute it back,
perhaps someone else would find it useful.
Wayne
On 8/30/07, Stephen More <[EMAIL PROTECTED]> wrote:
I would like to release some code as "open source", but I am not sure
which license to pick.
"Does your project currently use any open source code? If so, then you
may need to use the same license that the open source code uses, or
another license that is compatible with it."
Maven does a great job with figuring out dependencies. Based on these
dependencies is there a plugin that can identify what license could
be assigned to this project ?
-Thanks
Steve More
-
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]
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
any one...Emmanuel..you might have something on this..?
mfs wrote:
>
> Dear All,
>
> I am getting this strange behavior where even on a build-failure (as
> below) as shown in the Result, the success icon is shown against the
> project on "show-project" screen and same is the case with history screen
> against a project...and even no emails are sent as its intrepreting that
> the build is a success (dont know why) and no state change since last
> build..
>
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Share : PDFP
> [INFO]task-segment: [clean, install]
> [INFO]
>
> [INFO] [clean:clean]
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target\classes
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target\test-classes
> [INFO] Deleting directory C:\continuum\continuum_wd\8\target\site
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Compiling 18 source files to
> C:\continuum\continuum_wd\8\target\classes
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
> C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1,0]
> 'class' or 'interface' expected
>
>
>
> C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1,0]
> 'class' or 'interface' expected
>
>
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Aug 30 11:01:50 PDT 2007
> [INFO] Final Memory: 4M/8M
> [INFO]
>
>
>
--
View this message in context:
http://www.nabble.com/Strange---Success-icon-shown-and-no-emails-sent-in-case-of-build-failure-tf4355976.html#a12414714
Sent from the Continuum - Users mailing list archive at Nabble.com.
Raphaël,
Thank you for your reply, that outlined list your created of the
steps is exactly what I did, and a good bit more accurate than what I
typed in my last email,
"What i am not sure to understand is what you expected to have instead
of
what you got."
- Raphaël Piéroni
What I expected to have was a combined pom.xml of the the two
Archtypes, provided there would have been no conflicting elements
inside the two prototype prom.xml files.
For instance,
Say that the prototype pom.xml of the Java6Archetype I created would
contain the following unique lines:
...
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
...
prototype pom.xml of the Java6Archetype
And that the JUnit4Archetype prototype pom.xml would have the
following unique lines:
...
...
junit
junit
4.0
test
...
prototype pom.xml of the JUnit4Archetype
I was under the impression that if you ran "mvn archetype:create"
twice on the same resulting project (TestLayered), that the result
would be a pom.xml file that would contain:
- the build-plugin settings from the prototype pom.xml of the Java6Archetype
-and-
- the junit4 dependencies from the prototype pom.xml of the Unit4Archetype.
What lead me to believe this was the statement in the Guide to
Creating Archetypes documentation (which I mentioned in my previous
email) mainly:
An optional true tag makes it possible
to run the archetype:create even on existing projects.
Now my question is if there is indeed anyway to do what I mentioned
above, since it would allow me to very easily create a system that
would configure the project (for JUnit, Hibernate, Spring, etc...), by
running several different pre-configured archetypes on the same
project.
Thank you,
Andrew J. Leer
On 8/30/07, Raphaël Piéroni <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am not sure to well understand what you meant.
> Here comes what i have understood, plesae correct me if i am wrong:
> - you did mvn archetype:create -DarchetypeArtifactId=java6archetype
> -DartifactId=TestLayer
> - you obtained the TestLayer folder in the directory you executed the mvn
> comand
> - that folder contains the TestLayer project created from the choosen Java6
> archetype
> - you changed directory to that folder
> - you then did archetype:create -DarchetypeArtifactId=Junit4achetype
> -DartifactId=TestLayer
> - you obtained a modification of the TestLayer project's pom and file
> structure.
>
> What i am not sure to understand is what you expected to have instead of
> what you got.
>
> Regards,
>
> Raphaël Piéroni
>
> 2007/8/30, Andrew Leer <[EMAIL PROTECTED]>:
> >
> > I am certain that I have misinterpreted the meaning of this piece of
> > documentation:
> >
> > Guide to Creating Archetypes
> > - (http://maven.apache.org/guides/mini/guide-creating-archetypes.html)
> >| - 2. Create the archetype descriptor
> >
> > An optional true tag makes it
> > possible to run the
> > archetype:create even on existing projects.
> >
> > I thought that this meant that I could create several of my own
> > archetypes and than generate a single project; running the
> > archtype:create command over the generated project several times until
> > the accumulated properties of each archetype were all added to that
> > single project.
> >
> > Begin Example
> >
> > If I have the following Archetypes installed in M2_REPO:
> > - Java6Archetype
> > - JUnit4Archetype
> >
> > And I create a project called TestLayered Project using the
> > Java6Archetype above and the archetype:create command.
> >
> > I should then be able to run the JUnit4Archetype with the
> > archetype:create command over top of the existing TestLayered Project
> > resulting in a blending of the two archetypes within the TestLayered
> > Project.
> >
> > End Example
> >
> > This is what I believed the documentation meant by:
> >
> > "An optional true tag makes it
> > possible to run the
> > archetype:create even on existing projects."
> >
> > I now realize that this is wrong. Is there anyway to implement this
> > sort of "mixing" and "matching" or "layering" of Archtypes in a single
> > project?
> >
> > Also, what did the documentation mean by the statement above? I read
> > elsewhere that it has something to do with modular builds.
> >
> > Thank you,
> > Andrew J. Leer
> >
> > -
> > 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]
Just out of curiosity, how the heck would you figure this out? Seems like
this would be too complicated to do in software though I AM 100% FOR
replacing corporate legal teams with a Mojo! :D!
-aps
On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> Not that I know of. If you write it, please contribute it back,
> perhaps someone else would find it useful.
>
> Wayne
>
> On 8/30/07, Stephen More <[EMAIL PROTECTED]> wrote:
> > I would like to release some code as "open source", but I am not sure
> > which license to pick.
> >
> > "Does your project currently use any open source code? If so, then you
> > may need to use the same license that the open source code uses, or
> > another license that is compatible with it."
> >
> > Maven does a great job with figuring out dependencies. Based on these
> > dependencies is there a plugin that can identify what license could
> > be assigned to this project ?
> >
> >
> > -Thanks
> > Steve More
> >
> > -
> > 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]
>
>
--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson
Not that I know of. If you write it, please contribute it back,
perhaps someone else would find it useful.
Wayne
On 8/30/07, Stephen More <[EMAIL PROTECTED]> wrote:
> I would like to release some code as "open source", but I am not sure
> which license to pick.
>
> "Does your project currently use any open source code? If so, then you
> may need to use the same license that the open source code uses, or
> another license that is compatible with it."
>
> Maven does a great job with figuring out dependencies. Based on these
> dependencies is there a plugin that can identify what license could
> be assigned to this project ?
>
>
> -Thanks
> Steve More
>
> -
> 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]
Hello,
How can I apply an xslt to our /target/surefire-reports/TEST-*.xml
files?
In our effort to migrate from ant to maven, I need to apply an xslt
to our surefire XML reports. This xslt generates an sql file which we
import into a database to track our continuous integration status
over time.
Currently this is managed by the target in ant.
Thanks,
Josh
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Dear All,
I am getting this strange behavior where even on a build-failure (as below)
as shown in the Result, the success icon is shown against the project on
"show-project" screen and same is the case with history screen against a
project...and even no emails are sent as its intrepreting that the build is
a success (dont know why) and no state change since last build..
[INFO] Scanning for projects...
[INFO]
[INFO] Building Share : PDFP
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory C:\continuum\continuum_wd\8\target
[INFO] Deleting directory C:\continuum\continuum_wd\8\target\classes
[INFO] Deleting directory C:\continuum\continuum_wd\8\target\test-classes
[INFO] Deleting directory C:\continuum\continuum_wd\8\target\site
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 18 source files to
C:\continuum\continuum_wd\8\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1,0]
'class' or 'interface' expected
C:\continuum\continuum_wd\8\src\main\java\vaudit\pdfp\PdfField.java:[1,0]
'class' or 'interface' expected
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Thu Aug 30 11:01:50 PDT 2007
[INFO] Final Memory: 4M/8M
[INFO]
--
View this message in context:
http://www.nabble.com/Strange---Success-icon-shown-and-no-emails-sent-in-case-of-build-failure-tf4355976.html#a12412927
Sent from the Continuum - Users mailing list archive at Nabble.com.
And now i know why i did this without asking myself. It seems to be a common
practice to say something like i saw on jakarta taglibs:
http://jakarta.apache.org/taglibs/doc/string-doc/string-1.1.0/index.html
http://jakarta.apache.org/taglibs/doc/string-doc/string-1.1.0/index.html
>
> Follow these steps to configure your web application with this tag
> library:
>
> * Copy the tag library descriptor file to the /WEB-INF subdirectory of
> your web application.
> * Copy the tag library JAR file to the /WEB-INF/lib subdirectory of
> your web application.
> * Add a element to your web application deployment descriptor
> in /WEB-INF/web.xml like this:
>
>
>
> http://jakarta.apache.org/taglibs/string-1.1
> /WEB-INF/string.tld
>
>
--
View this message in context:
http://www.nabble.com/Dependency-on-a-tag-libary-and-its-descriptor-tf4355291s177.html#a12412915
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello Dennis,
i just found this line in the jsp spec 1.1:
5.2.1 Packaged Tag Libraries
JSP page authoring tools are required to accept a Tag Library
that is packaged as a JAR file.
When packaged sot he JAR file must have a tag library descriptor
file named META-INF/taglib.tld.
After all those years i have just learned something new. I always extracted
taglibs, added the taglib mappings to the web.xml and thats it. I do not
know why. Never asked myself.
And so i can ask myself from now on as well: why would i continue to want
that? And i can answer then: because i can.
But of course i will change this behaviour just from today on. :-)
Thank you a lot.
Dennis Lundberg-2 wrote:
>
> okrische wrote:
>> Hello,
>>
>> i have a project, which provides a tag library "mytaglib.jar". While the
>> tag
>> library is in development, the tag library descriptor "mytaglib.tld"
>> grows
>> and changes as well. It belongs together.
>>
>> I have another webapp project, which depends on this tag library and its
>> tld
>>
>> Reflecting the dependency to the tag library is simple. So, when i
>> compile
>> the project, the latest snapshot will be pulled from the repository. But
>> how
>> will i get the latest "mytaglib.tld" ?
>>
>> Extracting it from the jar could be an idea.? And putting it into the
>> WEB-INF directory of the webapp-project?
>
> I'm confused. Why would you want to extract the .tld file?
>
--
View this message in context:
http://www.nabble.com/Dependency-on-a-tag-libary-and-its-descriptor-tf4355291s177.html#a12412578
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Dear All,
Is there a way i can configure Continuum to send email notifications just to
1) the committer of the code
2) administrator
Write now the emails are being sent to the notifiers i have configured in
the pom.xml.
Thanks and Regards,
Farhan.
--
View this message in context:
http://www.nabble.com/Email-notification-to-just-the-committer-and-the-administrator-tf4355830.html#a12412470
Sent from the Continuum - Users mailing list archive at Nabble.com.
On Aug 30, 2007, at 12:17 PM, Farrukh Najmi wrote:
Joshua ChaitinPollak wrote:
Hello,
I'm still having trouble with getting embedded tomcat to compile
my JSPs.
What did you mean by "embedded tomcat"?
Is this a tomcat instance provided by an IDE like Netbeans?
No, not at all. I have a class in my own code that instantiates a
copy of tomcat to run and hardcodes a Context to run for our
application. Basically, we have a larger server application which
runs an embedded tomcat to manage our webapp. This works great with
Ant, but we are trying to move to Maven ASAP.
The problem is that no matter what I try, the Tomcat instance doesn't
seem to find all of the needed jars, and I get Jasper compiler errors.
Right now I'm trying to understand the difference between
javax.servlet:servlet-api and tomcat:servlet-api, and whether I
need both of them, or just one. I'm currently explicitly depending
on tomcat:servlet-api, but the javax dependency keeps being pulled
in transitively.
AFAIK you should only depend upon javax.servlet:servlet-api and
that should be done with dependency sub-element:
provided
I'm not running with an IDE's embedded tomcat, I'm running with my
own tomcat, so I don't think I should say 'provided'. I think I need
to provide all these Jars myself.
Can someone explain this to me? Do I need both? Should I exclude one?
HTH.
--
Regards,
Farrukh
Web: http://www.wellfleetsoftware.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I would like to release some code as "open source", but I am not sure
which license to pick.
"Does your project currently use any open source code? If so, then you
may need to use the same license that the open source code uses, or
another license that is compatible with it."
Maven does a great job with figuring out dependencies. Based on these
dependencies is there a plugin that can identify what license could
be assigned to this project ?
-Thanks
Steve More
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
okrische wrote:
Hello,
i have a project, which provides a tag library "mytaglib.jar". While the tag
library is in development, the tag library descriptor "mytaglib.tld" grows
and changes as well. It belongs together.
I have another webapp project, which depends on this tag library and its tld
Reflecting the dependency to the tag library is simple. So, when i compile
the project, the latest snapshot will be pulled from the repository. But how
will i get the latest "mytaglib.tld" ?
Extracting it from the jar could be an idea.? And putting it into the
WEB-INF directory of the webapp-project?
I'm confused. Why would you want to extract the .tld file?
Would i have to do that with each taglib dependency?
Thankful for ideas.
Cheers.
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The current pde-maven-plugin only produces zip format for the plugin build.
for the time being, you will need to manipulate that output zip file
to produce your expected jar file.
-D
On 8/30/07, malc <[EMAIL PROTECTED]> wrote:
>
> I have a simple plugin which I can export from eclipse no problem as a jar
> file. I have set up my pom.xml to be the same as that described on the usage
> page. However no jar gets created only a zip file and the structure inside
> the zip file is 1 level too deep to be able to use the zip file as is in
> eclipse plugins folder. ie the zip file is called something like
> com.alphabet.soup_1.1.0.zip and within it the top level folder is called
> com.alphabet.soup_1.1.0, with all of the plugin stuff below that.
>
> I have tried a number of different things to get round this and have made
> the following observations:
>
> 1. It seems that the generated build always does the clean, build.jars and
> zip.plugin targets. If I specify a target via the pom.xml ie
>
>
>
>build.update.jar
> K:\eclipseTarget\eclipse
> true
>
>build.update.jar
>
>
>
> it adds it to the existing command line with the above mentioned targets as
> -Dtarget=build.update.jar but doesn't seem to get executed.
>
> 2. using this in the configuration seems to have no effect :
>
>
>true
>
>
> 3. The sample plugin from the tutorial also builds a zp file which doesn't
> work directly in eclipse (seems to have the extra top level directory
> problem also)
>
> My version of eclipse is Version: 3.2.2
> Build id: M20070212-1330
>
> What can I do to get pde-maven to generate my plugin properly - help please
> its driving me crazy now. Any advice at all would be welcome.
> --
> View this message in context:
> http://www.nabble.com/pde-maven-trying-to-generate-a-simple-plugin.-tf4355402s177.html#a12411046
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> 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]
Hi,
I am not sure to well understand what you meant.
Here comes what i have understood, plesae correct me if i am wrong:
- you did mvn archetype:create -DarchetypeArtifactId=java6archetype
-DartifactId=TestLayer
- you obtained the TestLayer folder in the directory you executed the mvn
comand
- that folder contains the TestLayer project created from the choosen Java6
archetype
- you changed directory to that folder
- you then did archetype:create -DarchetypeArtifactId=Junit4achetype
-DartifactId=TestLayer
- you obtained a modification of the TestLayer project's pom and file
structure.
What i am not sure to understand is what you expected to have instead of
what you got.
Regards,
Raphaël Piéroni
2007/8/30, Andrew Leer <[EMAIL PROTECTED]>:
>
> I am certain that I have misinterpreted the meaning of this piece of
> documentation:
>
> Guide to Creating Archetypes
> - (http://maven.apache.org/guides/mini/guide-creating-archetypes.html)
>| - 2. Create the archetype descriptor
>
> An optional true tag makes it
> possible to run the
> archetype:create even on existing projects.
>
> I thought that this meant that I could create several of my own
> archetypes and than generate a single project; running the
> archtype:create command over the generated project several times until
> the accumulated properties of each archetype were all added to that
> single project.
>
> Begin Example
>
> If I have the following Archetypes installed in M2_REPO:
> - Java6Archetype
> - JUnit4Archetype
>
> And I create a project called TestLayered Project using the
> Java6Archetype above and the archetype:create command.
>
> I should then be able to run the JUnit4Archetype with the
> archetype:create command over top of the existing TestLayered Project
> resulting in a blending of the two archetypes within the TestLayered
> Project.
>
> End Example
>
> This is what I believed the documentation meant by:
>
> "An optional true tag makes it
> possible to run the
> archetype:create even on existing projects."
>
> I now realize that this is wrong. Is there anyway to implement this
> sort of "mixing" and "matching" or "layering" of Archtypes in a single
> project?
>
> Also, what did the documentation mean by the statement above? I read
> elsewhere that it has something to do with modular builds.
>
> Thank you,
> Andrew J. Leer
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
http://maven.apache.org/plugins/maven-eclipse-plugin/index.html
-aps
On 8/30/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> I guess I am confused, I can't find anything about the eclipse plugin to
> create the eclipse project files from my Maven structure.
>
> Can someone help with the URL that describes the usage of this plugin?
>
> On 8/30/07, Dan Tran <[EMAIL PROTECTED]> wrote:
> >
> > You poms are fine. I have seen this in my projects too.
> >
> > -D
> >
> > On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> > > Dan,
> > >
> > > I was absolutely convinced that the error was in my pom file. I'm
> > > maven newbie, so it's hard for me to distinguish what is plugin bug
> and
> > > what is my mistake :P
> > >
> > > I will create jira issue.
> > >
> > > Thanks again for your help.
> > >
> > > Regards,
> > > Marcin
> > >
> > > Dan Tran wrote:
> > > > from our last discussion, eclipse plugin requires
> > > > your ejb3 module installed on you local repo, this is a bug. So the
> > > > work around is
> > > > to run 'mvn install' at eleast once before invoking 'mvn
> > eclipse:eclipse'
> > > >
> > > > please file an issue against eclipse plugin
> > > >
> > > > On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> > > >
> > > >> Hello.
> > > >>
> > > >> I created 2 module simple example which can be downloaded from:
> > > >>
> > > >> http://www.nabble.com/attachment/12381781/0/example.zip
> > > >>
> > > >> When I execute 'mvn package' everything works ok. But when I
> execute
> > mvn
> > > >> eclipse:eclipse I ended up with error:
> > > >>
> > > >>[DEBUG] Unable to download the artifact from any repository
> > > >> Try downloading the file manually from the project website.
> > > >> Then, install it using the command:
> > > >> mvn install:install-file -DgroupId=
> > com.company.app.appserver
> > > >> -DartifactId=ejb3 \
> > > >> -Dversion=1.0-SNAPSHOT -Dpackaging=ejb
> > -Dfile=/path/to/file
> > > >>
> > > >> Why it occurs during 'mvn eclipse:eclipse' but not during 'mvn
> > package'?
> > > >>
> > > >> (I know that the workaround is to make 'mvn instal' but I would
> like
> > to
> > > >> avoid this)
> > > >>
> > > >> Regards,
> > > >> Marcin
> > > >>
> > > >>
> -
> > > >> 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]
> > > >
> > > >
> > > >
> > >
> > >
> > > -
> > > 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]
> >
> >
>
>
> --
>
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> http://www.myspace.com/djmick_dot_com
> http://www.myspace.com/sexybeotches
> http://www.thumpradio.com
> ---
>
--
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson
I guess I am confused, I can't find anything about the eclipse plugin to
create the eclipse project files from my Maven structure.
Can someone help with the URL that describes the usage of this plugin?
On 8/30/07, Dan Tran <[EMAIL PROTECTED]> wrote:
>
> You poms are fine. I have seen this in my projects too.
>
> -D
>
> On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> > Dan,
> >
> > I was absolutely convinced that the error was in my pom file. I'm
> > maven newbie, so it's hard for me to distinguish what is plugin bug and
> > what is my mistake :P
> >
> > I will create jira issue.
> >
> > Thanks again for your help.
> >
> > Regards,
> > Marcin
> >
> > Dan Tran wrote:
> > > from our last discussion, eclipse plugin requires
> > > your ejb3 module installed on you local repo, this is a bug. So the
> > > work around is
> > > to run 'mvn install' at eleast once before invoking 'mvn
> eclipse:eclipse'
> > >
> > > please file an issue against eclipse plugin
> > >
> > > On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> > >
> > >> Hello.
> > >>
> > >> I created 2 module simple example which can be downloaded from:
> > >>
> > >> http://www.nabble.com/attachment/12381781/0/example.zip
> > >>
> > >> When I execute 'mvn package' everything works ok. But when I execute
> mvn
> > >> eclipse:eclipse I ended up with error:
> > >>
> > >>[DEBUG] Unable to download the artifact from any repository
> > >> Try downloading the file manually from the project website.
> > >> Then, install it using the command:
> > >> mvn install:install-file -DgroupId=
> com.company.app.appserver
> > >> -DartifactId=ejb3 \
> > >> -Dversion=1.0-SNAPSHOT -Dpackaging=ejb
> -Dfile=/path/to/file
> > >>
> > >> Why it occurs during 'mvn eclipse:eclipse' but not during 'mvn
> package'?
> > >>
> > >> (I know that the workaround is to make 'mvn instal' but I would like
> to
> > >> avoid this)
> > >>
> > >> Regards,
> > >> Marcin
> > >>
> > >> -
> > >> 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]
> > >
> > >
> > >
> >
> >
> > -
> > 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]
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
Le jeudi 30 août 2007, Craig Ryan a écrit :
> Here is an Ant build.xml snippet using maven tasks:
>
> url="dav:http://fred:[EMAIL PROTECTED]" layout="default"/>
> version="1.0-beta-2"/>
>
>
>
>
>
> the above works fine, and does a PUT of my jar into my company maven2
> repo. The following however does not
> work. Note: this time I don't specify username:password in the
> repository URL, instead I use an tag.
>
> url="dav:http://maven.mycompany.ie"; layout="default">
>
>
> version="1.0-beta-2"/>
>
>
>
>
>
> The authentication tag seems to be ignored this time, no auth headers
> are sent and the PUT fails with a 401.
> Can someone please explain why this doesn't work?
Did you try not to use a repository reference but directly declare the
repository in the deploy task?
http://maven.mycompany.ie";
layout="default">
Hervé
>
> The above example is highly simplified, in my build system I'd prefer to
> user authentication tags instead of embedding
> auth data in the repository url if possible, and also I'm basically
> curious ;-)
>
> thanks,
> 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]
I am certain that I have misinterpreted the meaning of this piece of
documentation:
Guide to Creating Archetypes
- (http://maven.apache.org/guides/mini/guide-creating-archetypes.html)
| - 2. Create the archetype descriptor
An optional true tag makes it possible to
run the
archetype:create even on existing projects.
I thought that this meant that I could create several of my own
archetypes and than generate a single project; running the
archtype:create command over the generated project several times until
the accumulated properties of each archetype were all added to that
single project.
Begin Example
If I have the following Archetypes installed in M2_REPO:
- Java6Archetype
- JUnit4Archetype
And I create a project called TestLayered Project using the
Java6Archetype above and the archetype:create command.
I should then be able to run the JUnit4Archetype with the
archetype:create command over top of the existing TestLayered Project
resulting in a blending of the two archetypes within the TestLayered
Project.
End Example
This is what I believed the documentation meant by:
"An optional true tag makes it
possible to run the
archetype:create even on existing projects."
I now realize that this is wrong. Is there anyway to implement this
sort of "mixing" and "matching" or "layering" of Archtypes in a single
project?
Also, what did the documentation mean by the statement above? I read
elsewhere that it has something to do with modular builds.
Thank you,
Andrew J. Leer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
Not really sure scm:svn://localhost/svn/repos/pdfp is
a valid url.
The scheme is missing.
--
Olivier
-Message d'origine-
De : mfs [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 30 août 2007 18:39
À : [EMAIL PROTECTED]
Objet : Cannot checkout sourcesInvalid SCM URL
Hello Everyone,
I am getting this error on a build done through continuum...
Exception:
Cannot checkout sources.//localhost/pdfp url isn't a valid svn URL.
The scm url is invalid.
which i am not able to figure out why...any help is much appreciated..am using
maven 2 with sub-version..nyways have also pasted the contents of the pom files
below..Let me add that i am getting a build-fail email, on the emails
configured in my pom.xml..
Thanks in advance and Regards,
Farhan.
--
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
company.share
pdfp
1.X-SNAPSHOT
Share : PDFP
jar
scm:svn://localhost/svn/repos/pdfp
scm:svn://localhost/pdfp
http://localhost/svn/repos/pdfp
radams
Robert
[EMAIL PROTECTED]
continuum
mail
[EMAIL PROTECTED]
itext
itext
2.0.4
log4j
log4j
1.2.14
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
--
View this message in context:
http://www.nabble.com/Cannot-checkout-sourcesInvalid-SCM-URL-tf4355448.html#a12411221
Sent from the Continuum - Users mailing list archive at Nabble.com.
This e-mail, any attachments and the information contained therein ("this
message") are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
**
Ce message électronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci après "le message" ), sont confidentiels et
destinés exclusivement à l'usage de la personne à laquelle ils sont adressés.
Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur
et de le détruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressément autorisées de ce
message, sont interdites.
**
Hello Everyone,
I am getting this error on a build done through continuum...
Exception:
Cannot checkout sources.//localhost/pdfp url isn't a valid svn URL.
The scm url is invalid.
which i am not able to figure out why...any help is much appreciated..am
using maven 2 with sub-version..nyways have also pasted the contents of the
pom files below..Let me add that i am getting a build-fail email, on the
emails configured in my pom.xml..
Thanks in advance and Regards,
Farhan.
--
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
company.share
pdfp
1.X-SNAPSHOT
Share : PDFP
jar
scm:svn://localhost/svn/repos/pdfp
scm:svn://localhost/pdfp
http://localhost/svn/repos/pdfp
radams
Robert
[EMAIL PROTECTED]
continuum
mail
[EMAIL PROTECTED]
itext
itext
2.0.4
log4j
log4j
1.2.14
org.apache.maven.plugins
maven-compiler-plugin
1.5
1.5
--
View this message in context:
http://www.nabble.com/Cannot-checkout-sourcesInvalid-SCM-URL-tf4355448.html#a12411221
Sent from the Continuum - Users mailing list archive at Nabble.com.
I have a simple plugin which I can export from eclipse no problem as a jar
file. I have set up my pom.xml to be the same as that described on the usage
page. However no jar gets created only a zip file and the structure inside
the zip file is 1 level too deep to be able to use the zip file as is in
eclipse plugins folder. ie the zip file is called something like
com.alphabet.soup_1.1.0.zip and within it the top level folder is called
com.alphabet.soup_1.1.0, with all of the plugin stuff below that.
I have tried a number of different things to get round this and have made
the following observations:
1. It seems that the generated build always does the clean, build.jars and
zip.plugin targets. If I specify a target via the pom.xml ie
build.update.jar
K:\eclipseTarget\eclipse
true
build.update.jar
it adds it to the existing command line with the above mentioned targets as
-Dtarget=build.update.jar but doesn't seem to get executed.
2. using this in the configuration seems to have no effect :
true
3. The sample plugin from the tutorial also builds a zp file which doesn't
work directly in eclipse (seems to have the extra top level directory
problem also)
My version of eclipse is Version: 3.2.2
Build id: M20070212-1330
What can I do to get pde-maven to generate my plugin properly - help please
its driving me crazy now. Any advice at all would be welcome.
--
View this message in context:
http://www.nabble.com/pde-maven-trying-to-generate-a-simple-plugin.-tf4355402s177.html#a12411046
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello everybody.
i want to use the assembly plug-in to generate a tarball of the project I am
working on. Everything is working fine and this plug-in have just saved my
life...
But one of the things I haven't found while searching on the list and on the
examples, is how can I unpack a fileset. I got a zip file containing
different files. They have to be transfered at a specific place in the
assembly and have to be unpacked.
But, from what I have seen, I would need a fileset or a simple file. But
either of them offer the possibility to unpack.
Is there a possible workaround? Or maybe it can be a future enhencment to
the assembly descriptor/plugin.
Thanks in advance for helping me.
Marc
--
View this message in context:
http://www.nabble.com/Assembly-Plugin-question%2C-unpacking-a-fileset-tf4355399s177.html#a12411037
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Hilco,
Le mercredi 29 août 2007, Hilco Wijbenga a écrit :
> Hi all,
>
> I ran into something strange while using the Maven Ant Tasks (2.0.7).
> My Ant build now includes a POM which refers to a parent POM.
>
> If I have the parent POM available in my local repository everything
> works fine. If not, then the build fails because it can't download the
> parent POM. (If I use Maven instead of Maven Ant Tasks then it works
> regardless.)
>
> My settings.xml contains the remote repository's location and my
> build.xml contains:
>
>
>
>
> uri="urn:maven-artifact-ant">
>
>
>
>
>
> filesetId="maven-ant-tasks.dependency.fileset">
>
>url="http://maven.example.com/repository"/>
>
>
>
>
> Firstly, removing from build.xml fails the
> build. Apparently, settings.xml is ignored?
Can you precise how you declared this repository in your settings.xml?
Is it in a profile? Or is it a mirrorOf declaration? Or ...?
If you run ant with "-v" option, you'll see more precisely what is done.
>
> Secondly, why doesn't it download the parent POM? It's in the same
> repository as the JARs and those *are* downloaded (provided I've
> installed the parent POM locally).
Did you try not to use pom reference? Like:
If you can create a testcase (with file:// remote repositories), it will be
easier to help you.
Hervé
>
> Cheers,
> Hilco
>
> -
> 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]
Joshua ChaitinPollak wrote:
Hello,
I'm still having trouble with getting embedded tomcat to compile my JSPs.
What did you mean by "embedded tomcat"?
Is this a tomcat instance provided by an IDE like Netbeans?
Right now I'm trying to understand the difference between
javax.servlet:servlet-api and tomcat:servlet-api, and whether I need
both of them, or just one. I'm currently explicitly depending on
tomcat:servlet-api, but the javax dependency keeps being pulled in
transitively.
AFAIK you should only depend upon javax.servlet:servlet-api and that
should be done with dependency sub-element:
provided
Can someone explain this to me? Do I need both? Should I exclude one?
HTH.
--
Regards,
Farrukh
Web: http://www.wellfleetsoftware.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I have the same problem. Seems like a pretty significant issue -- the site
plugin looks totally broken. Anyone have workarounds for this?
On 8/27/07, Martin Alejandro Villalobos <[EMAIL PROTECTED]>
wrote:
>
> Hello, I have a question.
> I'm executing mvn site site:deploy on a project with several modules ,
> but... when the site is deployed, the links in the "Modules" section
> are right for the parent index, but are wrong for the the childs.
> All links are relative to childs.
> There is any way for generate this links in a right way?
>
> Thanks for all.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Here is an Ant build.xml snippet using maven tasks:
url="dav:http://fred:[EMAIL PROTECTED]" layout="default"/>
version="1.0-beta-2"/>
the above works fine, and does a PUT of my jar into my company maven2
repo. The following however does not
work. Note: this time I don't specify username:password in the
repository URL, instead I use an tag.
url="dav:http://maven.mycompany.ie"; layout="default">
version="1.0-beta-2"/>
The authentication tag seems to be ignored this time, no auth headers
are sent and the PUT fails with a 401.
Can someone please explain why this doesn't work?
The above example is highly simplified, in my build system I'd prefer to
user authentication tags instead of embedding
auth data in the repository url if possible, and also I'm basically
curious ;-)
thanks,
craig.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello,
i have a project, which provides a tag library "mytaglib.jar". While the tag
library is in development, the tag library descriptor "mytaglib.tld" grows
and changes as well. It belongs together.
I have another webapp project, which depends on this tag library and its tld
Reflecting the dependency to the tag library is simple. So, when i compile
the project, the latest snapshot will be pulled from the repository. But how
will i get the latest "mytaglib.tld" ?
Extracting it from the jar could be an idea.? And putting it into the
WEB-INF directory of the webapp-project?
Would i have to do that with each taglib dependency?
Thankful for ideas.
Cheers.
--
View this message in context:
http://www.nabble.com/Dependency-on-a-tag-libary-and-its-descriptor-tf4355291s177.html#a12410667
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello,
I'm still having trouble with getting embedded tomcat to compile my
JSPs. Right now I'm trying to understand the difference between
javax.servlet:servlet-api and tomcat:servlet-api, and whether I need
both of them, or just one. I'm currently explicitly depending on
tomcat:servlet-api, but the javax dependency keeps being pulled in
transitively.
Can someone explain this to me? Do I need both? Should I exclude one?
Thanks,
Josh
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
John,
I had a similar issue, where I wanted to copy my assembly to a network
drive, but only on the releng machines. I ended up using a manually
activated profile to do this. My deployment directory variable was set
during automatically activated profiles based on the platform it was
running on. I used something like classifiers to avoid name collisions
(my assembly id in the descriptor was "${osArch}-${osName}-dist"). This
may be of some use to you.
Andrew
buildMachine
maven-antrun-plugin
install
install
run
> -Original Message-
> From: John Coleman [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 29, 2007 4:23 AM
> To: Maven Users List
> Subject: RE: classifier for maven deploy plugin
>
> Perhaps I need to explain the issue further.
>
> While our WARs contain common core code packages, each one is
flavoured
> per client (typically providing custom images) and differing suits of
> JSPs.
>
> We are not interested in the install task as these WARs will never be
> shared off a repository. However, when we deploy the WARs to our
staging
> server, they must have unique names using the classifier concept. But
if
> we classify the WARs the deploy doesn't like it, and nor does the
jetty
> plugin.
>
> I have been trying to resolve this by generating an assembly zip, but
> the deploy task delivers the WAR. Ideally I'd like to be able to
deploy
> the assembly.
>
> Perhaps I should derive my own assembly-deploy plugin and inherit from
> the regular deploy plugin somehow? If so, how would I override the
> regular deploy task and replace it with my extended goal?
>
> Regards,
> John
>
>
> -Original Message-
> From: Dan Tran [mailto:[EMAIL PROTECTED]
> Sent: 28 August 2007 18:04
> To: Maven Users List
> Subject: Re: classifier for maven deploy plugin
>
> I am going to assume that you want to deploy artifacts that are not
> built by maven.
>
> You can create a pom and configure build-helper-maven-plugin to attach
> all
> your artifacts to maven, and finally call 'maven deploy'
>
> -D
>
>
>
> On 8/28/07, John Coleman <[EMAIL PROTECTED]>
> wrote:
> > Hi,
> >
> >
> >
> > Is there a way to use a classifier with the maven deploy plugin by
> > configuring the plugin in the pom rather that using command line
> > properties?
> >
> >
> >
> > TIA,
> >
> > John
> >
> >
> >
> >
> > Eurobase International Limited and its subsidiaries (Eurobase) are
> unable to exercise control over the content of information in E-Mails.
> Any views and opinions expressed may be personal to the sender and are
> not necessarily those of Eurobase. Eurobase will not enter into any
> contractual obligations in respect of any part of its business in any
> E-mail.
> >
> > Privileged / confidential information may be contained in this
message
> and /or any attachments. This E-mail is intended for the use of the
> addressee(s) only and may contain confidential information. If you are
> not the / an intended recipient, you are hereby notified that any use
or
> dissemination of this communication is strictly prohibited. If you
> receive this transmission in error, please notify us immediately, and
> then delete this E-mail.
> >
> > Neither the sender nor Eurobase accepts any liability whatsoever for
> any defects of any kind either in or arising from this E-mail
> transmission. E-Mail transmission cannot be guaranteed to be secure or
> error-free, as messages can be intercepted, lost, corrupted,
destroyed,
> contain viruses, or arrive late or incomplete. Eurobase does not
accept
> any responsibility for viruses and it is your responsibility to scan
any
> attachments.
> >
> > Eurobase Systems Limited is the main trading company in the Eurobase
> International Group; registered in England and Wales as company number
> 02251162; registered address: Essex House, 2 County Place, Chelmsford,
> Essex CM2 0RE, UK.
> >
> >
>
> -
> 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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
I am using continuum-1.1-beta2 to build two branches of a project. One
branch requires java 4 to build, and the other branch requires java 5.
If I try to build the java 4 branch with java 5 i get test failures.
Both projects use maven 2.0.6 to build.
So... I have set up two build profiles accordingly and linked the
projects accordingly. However when I try to build the java 4 branch I
get the same test failures I do as when I try to build it with java 5.
The build report I get back reports that the 1.4 jdk is indeed being
used. However if I build the project "manually" with the same 1.4 jdk
(ie, not through continuum) it works ok.
Could I be running into class loader or vm forking issues? I have tried
to play with the maven settings for running the tests like forking a new
vm process per test but it does not appear to have an impact.
So... anyone have any ideas? I can make the continuum instance available
if that helps.
Many thanks,
-Justin
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
You poms are fine. I have seen this in my projects too.
-D
On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> Dan,
>
> I was absolutely convinced that the error was in my pom file. I'm
> maven newbie, so it's hard for me to distinguish what is plugin bug and
> what is my mistake :P
>
> I will create jira issue.
>
> Thanks again for your help.
>
> Regards,
> Marcin
>
> Dan Tran wrote:
> > from our last discussion, eclipse plugin requires
> > your ejb3 module installed on you local repo, this is a bug. So the
> > work around is
> > to run 'mvn install' at eleast once before invoking 'mvn eclipse:eclipse'
> >
> > please file an issue against eclipse plugin
> >
> > On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> >
> >> Hello.
> >>
> >> I created 2 module simple example which can be downloaded from:
> >>
> >> http://www.nabble.com/attachment/12381781/0/example.zip
> >>
> >> When I execute 'mvn package' everything works ok. But when I execute mvn
> >> eclipse:eclipse I ended up with error:
> >>
> >>[DEBUG] Unable to download the artifact from any repository
> >> Try downloading the file manually from the project website.
> >> Then, install it using the command:
> >> mvn install:install-file -DgroupId=com.company.app.appserver
> >> -DartifactId=ejb3 \
> >> -Dversion=1.0-SNAPSHOT -Dpackaging=ejb -Dfile=/path/to/file
> >>
> >> Why it occurs during 'mvn eclipse:eclipse' but not during 'mvn package'?
> >>
> >> (I know that the workaround is to make 'mvn instal' but I would like to
> >> avoid this)
> >>
> >> Regards,
> >> Marcin
> >>
> >> -
> >> 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]
> >
> >
> >
>
>
> -
> 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]
Dan,
I was absolutely convinced that the error was in my pom file. I'm
maven newbie, so it's hard for me to distinguish what is plugin bug and
what is my mistake :P
I will create jira issue.
Thanks again for your help.
Regards,
Marcin
Dan Tran wrote:
from our last discussion, eclipse plugin requires
your ejb3 module installed on you local repo, this is a bug. So the
work around is
to run 'mvn install' at eleast once before invoking 'mvn eclipse:eclipse'
please file an issue against eclipse plugin
On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
Hello.
I created 2 module simple example which can be downloaded from:
http://www.nabble.com/attachment/12381781/0/example.zip
When I execute 'mvn package' everything works ok. But when I execute mvn
eclipse:eclipse I ended up with error:
[DEBUG] Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.company.app.appserver
-DartifactId=ejb3 \
-Dversion=1.0-SNAPSHOT -Dpackaging=ejb -Dfile=/path/to/file
Why it occurs during 'mvn eclipse:eclipse' but not during 'mvn package'?
(I know that the workaround is to make 'mvn instal' but I would like to
avoid this)
Regards,
Marcin
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Wendy's answer is the correct one. The documentation I pointed to is
buggy. I will file that in jira.
-Tim
Tim Kettler schrieb:
Hi,
Andrew Leer schrieb:
I don't understand where the archetype/test directories came from:
I guess your testproject has a groupId artifactId of:
com.mooo
archetype.test
and this gets converted to the shown package structure. See here [1].
It's a little bit cryptic but when you look at the example at the
bottom, you see that both groupId and artifactId are used for the
package hierachy.
-Tim
[1]
http://maven.apache.org/plugins/maven-archetype-plugin/examples/simple.html
Java6TestProjectFromAboveArcheType
| Java6TestArtifactFromArcheType.txt
| pom.xml
|
\---src
+---main
| \---java
| \---com
| \---mooo
| \---archetype <-- Where did this come from?
| \---test
| App.java
|
\---test
\---java
\---com
\---mooo
\---archetype <-- Where did this come from?
\---test
AppTest.java
I was actually expecting it to turn out more like the following:
(note that the archetype/test directories are both gone)
Java6TestProjectFromAboveArcheType
| Java6TestArtifactFromArcheType.txt
| pom.xml
|
\---src
+---main
| \---java
| \---com
| \---mooo
| App.java
|
\---test
\---java
\---com
\---mooo
AppTest.java
Again thank you,
I appreciate the help,
Andrew J. Leer
On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
Everything looks right/good to me.
What exactly is wrong, from your perspective? Its not clear what
you're getting vs what you expect to get.
Wayne
On 8/29/07, Andrew Leer <[EMAIL PROTECTED]> wrote:
See:
http://docs.codehaus.org/download/attachments/37533/MavenArchTypes_Template_N_Result2.zip
For full code of Archetype and resulting project from Archetype.
Thank you,
Andrew J. Leer
Hello, I am trying to make an archtype in mvn2.
My Archetype project has the following directory structure:
Java6ArchetypeProjectRoot
| Java6ArchetypeProject.txt
| pom.xml
| pom.xml~
|
+---src
| \---main
| \---resources
| +---archetype-resources
| | | pom.xml
| | |
| | \---src
| | +---main
| | | \---java
| | | App.java
| | |
| | \---test
| | \---java
| | AppTest.java
| |
| \---META-INF
| \---maven
| archetype.xml
| archetype.xml~
|
\---target
| maven-archetype-java-6-1.0-SNAPSHOT.jar
|
\---classes
+---archetype-resources
| | .pom.xml.swp
| | pom.xml
| |
| \---src
| +---main
| | \---java
| | App.java
| |
| \---test
| \---java
| AppTest.java
|
\---META-INF
\---maven
archetype.xml
I then installed the new Archetype in the repository using "mvn
install".
When I attempt to generate the project using the command:
mvn archetype:create
-DarchetypeGroupId=com.mooo.mv.archetype.compilerversion
-DarchetypeArtifactId=maven-archetype-java-6
-DarchetypeVersion=1.0-SNAPSHOT
-DgroupId=com.mooo.archetype.test
-DartifactId=Java6TestArtifact
I receive the following "flawed" directory structure:
(flawed mainly because of the placement of AppTest.java in
src\main\java\moo\archetype\test\AppTest.java
Java6TestProjectFromAboveArcheType
| Java6TestArtifactFromArcheType.txt
| pom.xml
|
\---src
+---main
| \---java
| \---com
| \---mooo
| \---archetype
| \---test
| App.java
|
\---test
\---java
\---com
\---mooo
\---archetype
\---test
AppTest.java
My archetype.xml looks like the following:
maven-archetype-java-6src/main/java/App.javasrc/test/java/AppTest.javatrue
Thank you,
Andrew J. Leer
P.S. Thank the DOS "tree" command for generating that directory
structure for me.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Thank you!
I never thought to look at the command line for my mistake. I will
do that next time!
On 8/30/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 8/30/07, Andrew Leer <[EMAIL PROTECTED]> wrote:
> > I don't understand where the archetype/test directories came from:
>
> Earlier, you wrote:
> mvn archetype:create
> > -DarchetypeGroupId=com.mooo.mv.archetype.compilerversion
> > -DarchetypeArtifactId=maven-archetype-java-6
> > -DarchetypeVersion=1.0-SNAPSHOT
> > -DgroupId=com.mooo.archetype.test
> > -DartifactId=Java6TestArtifact
>
> The groupId you supplied was used as the package structure. Use
> -DpackageName if you want the package to be different from the
> groupId.
>
> http://maven.apache.org/plugins/maven-archetype-plugin/create-mojo.html
>
> --
> Wendy
>
> -
> 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]
Hi,
Andrew Leer schrieb:
I don't understand where the archetype/test directories came from:
I guess your testproject has a groupId artifactId of:
com.mooo
archetype.test
and this gets converted to the shown package structure. See here [1].
It's a little bit cryptic but when you look at the example at the
bottom, you see that both groupId and artifactId are used for the
package hierachy.
-Tim
[1]
http://maven.apache.org/plugins/maven-archetype-plugin/examples/simple.html
Java6TestProjectFromAboveArcheType
| Java6TestArtifactFromArcheType.txt
| pom.xml
|
\---src
+---main
| \---java
| \---com
| \---mooo
| \---archetype <-- Where did this come from?
| \---test
| App.java
|
\---test
\---java
\---com
\---mooo
\---archetype <-- Where did this come from?
\---test
AppTest.java
I was actually expecting it to turn out more like the following:
(note that the archetype/test directories are both gone)
Java6TestProjectFromAboveArcheType
| Java6TestArtifactFromArcheType.txt
| pom.xml
|
\---src
+---main
| \---java
| \---com
| \---mooo
| App.java
|
\---test
\---java
\---com
\---mooo
AppTest.java
Again thank you,
I appreciate the help,
Andrew J. Leer
On 8/30/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
Everything looks right/good to me.
What exactly is wrong, from your perspective? Its not clear what
you're getting vs what you expect to get.
Wayne
On 8/29/07, Andrew Leer <[EMAIL PROTECTED]> wrote:
See:
http://docs.codehaus.org/download/attachments/37533/MavenArchTypes_Template_N_Result2.zip
For full code of Archetype and resulting project from Archetype.
Thank you,
Andrew J. Leer
Hello, I am trying to make an archtype in mvn2.
My Archetype project has the following directory structure:
Java6ArchetypeProjectRoot
| Java6ArchetypeProject.txt
| pom.xml
| pom.xml~
|
+---src
| \---main
| \---resources
| +---archetype-resources
| | | pom.xml
| | |
| | \---src
| | +---main
| | | \---java
| | | App.java
| | |
| | \---test
| | \---java
| | AppTest.java
| |
| \---META-INF
| \---maven
| archetype.xml
| archetype.xml~
|
\---target
| maven-archetype-java-6-1.0-SNAPSHOT.jar
|
\---classes
+---archetype-resources
| | .pom.xml.swp
| | pom.xml
| |
| \---src
| +---main
| | \---java
| | App.java
| |
| \---test
| \---java
| AppTest.java
|
\---META-INF
\---maven
archetype.xml
I then installed the new Archetype in the repository using "mvn install".
When I attempt to generate the project using the command:
mvn archetype:create
-DarchetypeGroupId=com.mooo.mv.archetype.compilerversion
-DarchetypeArtifactId=maven-archetype-java-6
-DarchetypeVersion=1.0-SNAPSHOT
-DgroupId=com.mooo.archetype.test
-DartifactId=Java6TestArtifact
I receive the following "flawed" directory structure:
(flawed mainly because of the placement of AppTest.java in
src\main\java\moo\archetype\test\AppTest.java
Java6TestProjectFromAboveArcheType
| Java6TestArtifactFromArcheType.txt
| pom.xml
|
\---src
+---main
| \---java
| \---com
| \---mooo
| \---archetype
| \---test
| App.java
|
\---test
\---java
\---com
\---mooo
\---archetype
\---test
AppTest.java
My archetype.xml looks like the following:
maven-archetype-java-6src/main/java/App.javasrc/test/java/AppTest.javatrue
Thank you,
Andrew J. Leer
P.S. Thank the DOS "tree" command for generating that directory
structure for me.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAI
On 8/30/07, Andrew Leer <[EMAIL PROTECTED]> wrote:
> I don't understand where the archetype/test directories came from:
Earlier, you wrote:
mvn archetype:create
> -DarchetypeGroupId=com.mooo.mv.archetype.compilerversion
> -DarchetypeArtifactId=maven-archetype-java-6
> -DarchetypeVersion=1.0-SNAPSHOT
> -DgroupId=com.mooo.archetype.test
> -DartifactId=Java6TestArtifact
The groupId you supplied was used as the package structure. Use
-DpackageName if you want the package to be different from the
groupId.
http://maven.apache.org/plugins/maven-archetype-plugin/create-mojo.html
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
from our last discussion, eclipse plugin requires
your ejb3 module installed on you local repo, this is a bug. So the
work around is
to run 'mvn install' at eleast once before invoking 'mvn eclipse:eclipse'
please file an issue against eclipse plugin
On 8/30/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> Hello.
>
> I created 2 module simple example which can be downloaded from:
>
> http://www.nabble.com/attachment/12381781/0/example.zip
>
> When I execute 'mvn package' everything works ok. But when I execute mvn
> eclipse:eclipse I ended up with error:
>
>[DEBUG] Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=com.company.app.appserver
> -DartifactId=ejb3 \
> -Dversion=1.0-SNAPSHOT -Dpackaging=ejb -Dfile=/path/to/file
>
> Why it occurs during 'mvn eclipse:eclipse' but not during 'mvn package'?
>
> (I know that the workaround is to make 'mvn instal' but I would like to
> avoid this)
>
> Regards,
> Marcin
>
> -
> 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]
On Thu, Aug 30, 2007 at 01:36:38PM +0200, Emmanuel Venisse wrote:
>
>
> Julien Stern a écrit :
> >On Thu, Aug 30, 2007 at 03:23:13AM -0700, Ionut S wrote:
> >>Hi,
> >>I don't know for what reason one of our projects (shown when you hit
> >>"Show projects" link) show as "Build in error" although the last 10 or so
> >>builds are successful.
> >>
> >>Did anybody had this problem ?
> >
> >Yes, this happens to us about twice a day with 1.1
> >It may be related to http://jira.codehaus.org/browse/CONTINUUM-1384
> >
> >You may want to check your logs to see if this is the same issue
> >or a different one.
>
Emmanuel,
> Do you have it with beta-2 too?
sorry, I haven't installed beta-2 yet. I will install it and let
you know.
> What is your default schedule?
Our default schedule is short (15 minutes) with many projects (> 200).
That's probably why we trigger this issue often.
> What is the max path length for your files?
I'm not sure I understand this question.
If you mean the max length of the absolute unix file path from the cvs
root, I'd hazard a guess as between 128 and 256.
I've taken a very quick look at the continuum code. I would tend to
think that this issue may be related to a project state that is not set back
to the correct value because two concurrent threads try to modify it
(the thread that performs the scm update and the thread that queues the
builds ?)
Maybe (just maybe, really :) ) in the class
UpdateWorkingDirectoryFromScmContinuumAction.java the latest
store.updateProject( project ) could fail, leaving an inconsistent
state ?
Again, this is a wild guess that could be totally wrong, the continuum
code is too complex to be understood after a quick look.
Regards,
--
Julien
This interpolated pom is generated in maven 1.1 when you deploy your artifact.
The code is in the artifact plugin
Arnaud
On 30/08/2007, Ataul Wadood Ahmad <[EMAIL PROTECTED]> wrote:
> Hi,
>
> sorry for the case that this question has already been answered.
> Unfortunately I didn´t find any search tool to search through the mail
> archive on the maven web site.
>
> Question:
> Is there a way (in maven 1) to generate the effective project.xml (with
> resolved variables and parent hierarchies).
>
> Thanks for your answers in advance.
>
> Regards,
> Ataul
>
> --
> Ataul W. Ahmad
> -Certified Project Management Associate (GPM, IPMA)-
> -Sun Certified Java Developer-
>
> email: [EMAIL PROTECTED]
> Fon: +49 177 829 87 39
> Fax: +49 571 398 13 77
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
..
Arnaud HERITIER
..
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I have a maven project called foo-server which produces a war.
I am looking for guidance on best practices for the following questions:
* What is the best practice for distributing a packaged release of
the foo-server project such that it is really simple for any
deployment to deploy it in as many web containers as possible.
o At present my thinking is to simply deploy the foo-server
project to a publicly accessible maven repo.
o I am aware that the http://cargo.codehaus.org/Downloads
project provides support for making deployment into many
containers simple.
o I am just not sure what is the ideal way to provide most
painless installation of foo-server into a desired web container
* What is the best practice for providing support for guided
installation of foo-server that provides the ease of popular
installers like InstallShield and takes care of customizing any
configuration files based upon user responses and ultimately
deploying the foo-bar project in the specified web container.
Thanks for your help.
--
Regards,
Farrukh
Web: http://www.wellfleetsoftware.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
sorry for the case that this question has already been answered.
Unfortunately I didn´t find any search tool to search through the mail
archive on the maven web site.
Question:
Is there a way (in maven 1) to generate the effective project.xml (with
resolved variables and parent hierarchies).
Thanks for your answers in advance.
Regards,
Ataul
--
Ataul W. Ahmad
-Certified Project Management Associate (GPM, IPMA)-
-Sun Certified Java Developer-
email: [EMAIL PROTECTED]
Fon: +49 177 829 87 39
Fax: +49 571 398 13 77
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Roger Ye schrieb:
Hi,
Hi,
I'm new to Maven, and now have a basic understanding of the Goal:Phase
notation in Maven to do sth.
That's not quite correct. Each packaging (for example jar) has a
lifecycle associated to it. This lifecylce consists of a sequence of
phases. So when you do 'mvn install' you tell maven to execute the
lifecylce-phase named 'install' and not to invoke the install-plugin.
The notation you used above is used for executing a goal (mojo) of a
plugin directly. So it should read plugin:goal.
My question is, regarding an unfamiliar goal, how can I know what phases are
available?
There is a detailed description of the default build-lifecylce available
here [1]. Every site of a plugin has a report 'Project Reports/Plugin
Documentation' that lists all the goals of the plugin. The plugins
maintained by the maven developers are listed here [2]. And many other
plugins are available at the mojo project over codehaus.org [3].
I do think there should be a common way for all the maven goals to provide
some help information, e.g. the usage of the goal and all its available
phases and their purposes, respectively.
e.g. for every shell command we have the -h or --help option to get help and
usage information, then what about we incorporate this convention into the
maven world and let every goal define a phase named "help" to do that?
The 'describe' goal of the maven-help-plugin can do this, it lists
information about other plugins. It is used like this 'mvn help:describe
-Dplugin=deploy -Dfull'. This will output the available goals of the
deploy-plugin together with the available parameters, but the formating
is not very user friendly.
Thanks
Roger
-Tim
[1]
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
[2] http://maven.apache.org/plugins/
[3] http://mojo.codehaus.org/plugins.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello.
I created 2 module simple example which can be downloaded from:
http://www.nabble.com/attachment/12381781/0/example.zip
When I execute 'mvn package' everything works ok. But when I execute mvn
eclipse:eclipse I ended up with error:
[DEBUG] Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.company.app.appserver
-DartifactId=ejb3 \
-Dversion=1.0-SNAPSHOT -Dpackaging=ejb -Dfile=/path/to/file
Why it occurs during 'mvn eclipse:eclipse' but not during 'mvn package'?
(I know that the workaround is to make 'mvn instal' but I would like to
avoid this)
Regards,
Marcin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Dan,
Thanks for your continuous help. I think it is a subject for another
thread...
Regards,
Marcin
Dan Tran wrote:
I ran into the same thing, and ended up to run
mvn installfirst
then
mvn eclipse:eclipse
-D
On 8/29/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
Dan, thanks for checking my example.
I'm sure that I use 2.4 version. In debug mode I can see:
[INFO] Building ejb3
.
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse' -->
But now I see that the problem is not around skipping module. In debug
output I can see line:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse' -->
but this I can see only for ejb3 module. I cannot see it for ear module
because it fails before:
[DEBUG] Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.company.app.appserver
-DartifactId=ejb3 \
-Dversion=1.0-SNAPSHOT -Dpackaging=ejb -Dfile=/path/to/file
It never fail when I execute 'mvn package'. But it fail during 'mvn
eclipse:eclipse'. That's why I decide to skip that module for mvn
eclipse:eclipse. Now I see that I cannot get rid of that problem by
skipping module, but I need to do something else.
The problem is that I have no idea why it fails during 'mvn
eclipse:eclipse'...
Regards,
Marcin
Dan Tran wrote:
Marcin, I am not able to reproduce your issue at my side using your example.
the only thing i can think of is you are using the wrong eclipse
plugin version prior to 2.4.
you may want to define eclipse plugin at the top level pom with
version configured.
and you still need to configure skip individually per child project.
-D
On 8/28/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
Dan, thanks for response.
I've reproduced it in two simple as possible module set. See atachement.
One is an ejb packaging project and the second is ear packaging project.
The second one use skip flag:
org.apache.maven.plugins
maven-eclipse-plugin
true
When I execute 'mvn eclipse:eclipse' for top level pom then ear
packaging project is not skipped.
Regards,
Marcin
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi:
Take a look at the help plugin, the help:describe goal gives you all you want ;)
http://maven.apache.org/plugins/maven-help-plugin/describe-mojo.html
Regards.
-Mensaje original-
De: [EMAIL PROTECTED] en nombre de Roger Ye
Enviado el: jue 30/08/2007 10:46
Para: Maven Users List
Asunto: Help Info for Goal?
Hi,
I'm new to Maven, and now have a basic understanding of the Goal:Phase
notation in Maven to do sth.
My question is, regarding an unfamiliar goal, how can I know what phases are
available?
I do think there should be a common way for all the maven goals to provide
some help information, e.g. the usage of the goal and all its available
phases and their purposes, respectively.
e.g. for every shell command we have the -h or --help option to get help and
usage information, then what about we incorporate this convention into the
maven world and let every goal define a phase named "help" to do that?
Thanks
Roger
--
This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail
in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender does
not warrant that this transmission is virus-free and will not be liable for
any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener informacion
confidencial destinada solamente a la(s) persona(s) mencionadas
anteriormente. Pueden estar protegidos por secreto profesional Si usted
recibe este correo electronico por error, gracias de informar inmediatamente
al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos
Origin no se hace responsable por su contenido. Su contenido no constituye
ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por
ambas partes.
Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor
no puede garantizar nada al respecto y no sera responsable de cualesquiera
danos que puedan resultar de una transmision de virus
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I'm new to Maven, and now have a basic understanding of the Goal:Phase
notation in Maven to do sth.
My question is, regarding an unfamiliar goal, how can I know what phases are
available?
I do think there should be a common way for all the maven goals to provide
some help information, e.g. the usage of the goal and all its available
phases and their purposes, respectively.
e.g. for every shell command we have the -h or --help option to get help and
usage information, then what about we incorporate this convention into the
maven world and let every goal define a phase named "help" to do that?
Thanks
Roger
Hi,
sounds like a bug. Could be related with or the same as this one [1].
If you think it's unrelated, create a simple test project that shows the
behaviour and file a new bugreport in jira [2].
-Tim
[1] http://jira.codehaus.org/browse/MRESOURCES-20
[2] http://jira.codehaus.org/browse/MRESOURCES
Nathan Maves schrieb:
Not sure but I think this is a bug.
I have a place holder in a spring config file named ${jdbc.url}
With filtering set to true for this resource ${jdbc.url} gets replaced by
the
http://maven.apache.org
specified in the pom file. Anyone else ever seen this or is this the
intended use of filtering?
Nathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I ran into the same thing, and ended up to run
mvn installfirst
then
mvn eclipse:eclipse
-D
On 8/29/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> Dan, thanks for checking my example.
>
> I'm sure that I use 2.4 version. In debug mode I can see:
>
>[INFO] Building ejb3
>.
>[DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse' -->
>
> But now I see that the problem is not around skipping module. In debug
> output I can see line:
>
>[DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-eclipse-plugin:2.4:eclipse' -->
>
> but this I can see only for ejb3 module. I cannot see it for ear module
> because it fails before:
>
>[DEBUG] Unable to download the artifact from any repository
>Try downloading the file manually from the project website.
>Then, install it using the command:
>mvn install:install-file -DgroupId=com.company.app.appserver
> -DartifactId=ejb3 \
>-Dversion=1.0-SNAPSHOT -Dpackaging=ejb -Dfile=/path/to/file
>
> It never fail when I execute 'mvn package'. But it fail during 'mvn
> eclipse:eclipse'. That's why I decide to skip that module for mvn
> eclipse:eclipse. Now I see that I cannot get rid of that problem by
> skipping module, but I need to do something else.
>
> The problem is that I have no idea why it fails during 'mvn
> eclipse:eclipse'...
>
> Regards,
> Marcin
>
>
> Dan Tran wrote:
> > Marcin, I am not able to reproduce your issue at my side using your example.
> >
> > the only thing i can think of is you are using the wrong eclipse
> > plugin version prior to 2.4.
> >
> > you may want to define eclipse plugin at the top level pom with
> > version configured.
> > and you still need to configure skip individually per child project.
> >
> > -D
> >
> > On 8/28/07, Marcin Waldowski <[EMAIL PROTECTED]> wrote:
> >
> >> Dan, thanks for response.
> >>
> >> I've reproduced it in two simple as possible module set. See atachement.
> >> One is an ejb packaging project and the second is ear packaging project.
> >> The second one use skip flag:
> >>
> >>org.apache.maven.plugins
> >>maven-eclipse-plugin
> >>
> >>true
> >>
> >>
> >>
> >> When I execute 'mvn eclipse:eclipse' for top level pom then ear
> >> packaging project is not skipped.
> >>
> >> Regards,
> >> Marcin
> >>
>
> -
> 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]
Hi,
I can't say if this is the final root of your problem but you should
start by fixing the repository definitions in your settings.xml and see
if that helps:
Srinivasan Chikkala schrieb:
Any help on how to get the latest maven-ant-plugin (
maven-ant-plugin-2.0-SNAPSHOT.jar) ?
I am trying to use the latest maven-ant-plugin, but when I execute "mvn
ant:ant" after setting the settings.xml entry
repo1
http://repo1.maven.org/maven2
central
'http://repo1.maven.org/maven2' *is* the URL of central, so you are
effectivly mirroring central with itself. You can savely just leave that
definition out.
snapshot.apache.org
http://people.apache.org/maven-snapshot-repository
central
'http://people.apache.org/maven-snapshot-repository' *is not* a mirror
of central. It contains just the snapshot releases of ASF artifacts.
This should just be a regular repository definition in your settings [1].
-Tim
[1]
http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
[...]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
