Re: Maven PDF support

[Markku Saarela]

For me PDF plugin is working with Markdown:


  org.apache.maven.plugins
  maven-pdf-plugin
  1.2
  

  pdf
  site
  
pdf
  
  
${project.build.directory}
  

  
  

org.apache.maven.doxia
doxia-module-markdown
  1.4

  

  


Cheers,

Markku

On 12/19/2013 12:00 PM, Robert Wettergren wrote:

We have a need to archive site documentation (markdown) and Javadoc for
each release so I thought I'd generate these as pdf.
To my surprise this turned out to be really difficult.

The maven-pdf-plugin doesn't support markdown.
It's also unable to aggregate reports, like Javadoc, due to
http://jira.codehaus.org/browse/MPDF-48
The doxia-maven-plugin can produce pdf but requires new xml 
descriptors.
However, Doxia can only consume markdown through doxia-module-markdown and
that only extends the site plugin.
The site plugin doesn't generate pdf.

The maven javadoc plugin can produce pdf by configuring a doclet.
However, I have a requirement to inject the project version in the PDF and
none of the doclets I've tried (pdfdoclet, texdoclet and aurigadoclet) seem
able to do this without adding new configuration files.

There are currently two things I can't do:
1. Produce PDF from Markdown
2. Product PDF Javadoc containing the project version.

Does anybody know a way of doing these things?

Thanks,
Robert




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven PDF support

[Markku Saarela]

Hi,

At least I can produce PDF from Markdown:


  org.apache.maven.plugins
  maven-pdf-plugin
  1.2
  

  pdf
  site
  
pdf
  
  

${project.build.directory}
  

  
  

  org.apache.maven.doxia
  doxia-module-markdown
  1.4

  

  



Markku


2013/12/19 Robert Wettergren 

> We have a need to archive site documentation (markdown) and Javadoc for
> each release so I thought I'd generate these as pdf.
> To my surprise this turned out to be really difficult.
>
> The maven-pdf-plugin doesn't support markdown.
> It's also unable to aggregate reports, like Javadoc, due to
> http://jira.codehaus.org/browse/MPDF-48
> The doxia-maven-plugin can produce pdf but requires new xml 
> descriptors.
> However, Doxia can only consume markdown through doxia-module-markdown and
> that only extends the site plugin.
> The site plugin doesn't generate pdf.
>
> The maven javadoc plugin can produce pdf by configuring a doclet.
> However, I have a requirement to inject the project version in the PDF and
> none of the doclets I've tried (pdfdoclet, texdoclet and aurigadoclet) seem
> able to do this without adding new configuration files.
>
> There are currently two things I can't do:
> 1. Produce PDF from Markdown
> 2. Product PDF Javadoc containing the project version.
>
> Does anybody know a way of doing these things?
>
> Thanks,
> Robert
>

Re: issues when disabling settings.xml

[Markku Saarela]

Install local Nexus in you machine and add work Nexus as proxy 
repository in it and then only one setting.xml works.

It also gives you freedom to work totally offline.

Cheers,
Markku
On 09/24/2013 03:31 AM, Jamie Archibald wrote:

I typically work behind a Nexus server at work which I use a settings.xml
file. When I come home I remove the settings.xml from my m2 folder.

As soon as I do this I can no longer resolve my maven dependencies that are
my work modules, even though they show up in my m2 repo.

When I put the settings.xml back into my m2 repo the dependencies can
resolve.

This happens with both snapshots and non-snapshots.

What am I missing here?




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why is properties-maven-plugin still in alpha?

[Markku Saarela]

Plugins are development time tools and not deliverables to the customer. 
So customer should not care how(by which plugin versions) artifacts are 
build. Therefore never reveal versions of the build tools to the 
customer :-)


Markku

On 02/26/2013 12:34 AM, Matthew Adams wrote:

Ok.  At least it's not a snapshot.

I'm more worried about the client's perception than anything, btw.  I'll
just have to explain about snapshots v. releases etc.


On Mon, Feb 25, 2013 at 9:45 AM, Benson Margulies wrote:


There are no 'powers that be'. There are volunteers. In the case of
the properties-maven-plugin, those are volunteers at the codehaus mojo
project, not the Apache Maven project. You really shouldn't let the
word 'alpha' bother you.

On Mon, Feb 25, 2013 at 9:33 AM, Matthew Adams 
wrote:

The ORM plugin is not going fubar.  I'm simply using its schema

generation

capabilities for my entities during my process-classes phase, and I just
happen to be using derby embedded to do it.  Derby, by design, will

produce

a derby.log file in the current working directory unless you take steps

to

avoid it, one of which is to set the system property
derby.stream.error.field to something other than its default value.  I

find

that setting it to java.lang.System.out is just jim-dandy.

In fact, I have different profiles for different ORMs & databases, and

they

*all* produce derby.log files when producing the schema against derby.

Can we simply have the powers that be promote properties-maven-plugin to

a

GA release, or move the functionality of the set-system-properties goal

to

build-helper-maven-plugin?


On Sun, Feb 24, 2013 at 8:43 AM, Martin Gainty 

wrote:

Matthew and Frederic

properties-maven-plugin has no hardcoded reference to derby.log

If you could identify the ORM maven-plugin groupId,artifactId,version

you

are implementing ..we could take a look at where its going fubar

-M


Date: Sun, 24 Feb 2013 08:25:26 +
Subject: Re: Why is properties-maven-plugin still in alpha?
From: stephen.alan.conno...@gmail.com
To: users@maven.apache.org

Fail safe has the same config options, and perhaps your ORM's maven

plugin

needs an enhancement ;-)

On Sunday, 24 February 2013, Matthew Adams wrote:


Good suggestion, but I need it for not just that (and besides, you

should

be using failsafe for integration tests, not surefire). But also I

need

that property set for database schema generation via my ORM's Maven

plugin,

which happens during the process-classes phase.


On Fri, Feb 22, 2013 at 10:58 PM, Dan Tran 

wrote:

for you case, you should pass the system property directly into

surefire

-D

On Fri, Feb 22, 2013 at 7:33 PM, Matthew Adams <

matt...@matthewadams.me>

wrote:

Hmmm. I'm using the goal
set-system-properties<

http://mojo.codehaus.org/properties-maven-plugin/set-system-properties-mojo.html

and
specifying a phase explicitly. Seems to work fine.

For the curious, my use case is trying to get rid of the

annoying

derby.log

file during my integration-test phase by using the derby system
property derby.stream.error.field=java.lang.System.out.

Maybe we could move the set-system-properties goal over to the
build-helper-maven-plugin<

http://mojo.codehaus.org/build-helper-maven-plugin/>.

Seems like a good place for it.

Works like a charm when you set it like this:


derby

derby
derby




org.codehaus.mojo
properties-maven-plugin



set-system-properties

initialize



derby.stream.error.field
java.lang.System.out













On Fri, Feb 22, 2013 at 9:59 AM, Frédéric Camblor <

fcamb...@gmail.com

wrote:


Hi !

I *think* this is because this plugin is shooting you in the

foot, by

making you think it will *always* load externalized properties

whereas

it

won't be the case.
For instance, during call of direct plugin goal (like

release:prepare

/

release:perform), the plugin won't be binded to any phases =>

properties

won't be loaded / made available.

I think this was based on a good idea at the beginning, but is

not

really

applicable.

Cheers,
Frédéric

Frédéric Camblor 

Bordeaux JUG  Leader
Jenkins  community member & plugin

commiter



On Fri, Feb 22, 2013 at 4:39 PM, Matthew Adams <

matt...@matthewadams.me


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




--
mailto:matt...@matthewadams.me 
skype:matthewadams12
googletalk:matt...@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubsc

Re: Why does mvn compiile using java 1.3?

[Markku Saarela]

I was only saying that why organizations are not moving to JDK 7. Lot of 
those organizations has policy to use only that JDK also for devepment , 
so you cannot install JDK 7.


I know you can run Maven over Java7 with older projects with some 
restrictions.


One is if you project use jasper-reports-plugin  which generates classes 
with that Java version which you are running Maven and then fails to use 
them because the Java class files are version 51.0  and 50,0 is required 
and build fails.


MArkku

On 11/29/2012 06:46 PM, Ron Wheeler wrote:

On 29/11/2012 10:17 AM, Markku Saarela wrote:
People is stuck for old Java versions due to the fact that for 
example organizations are using IBM WebSphere and do not upgrade 
those immediately when new version of WAS is released.  WAS 6.1 which 
was released in 2006 and just add support for JDK 1.5 not 1.6. It is 
WAS 7 which has JDK 6 support build in from beginning 2008. Just 
latest WAS 8.5 has possibility to use JDK 7.


Lot of organizations is still running with WAS 6 .
You are saying that for those organizations, Java 6 and 7 broke upward 
compatibility?
We never had that problem but I guess IBM's coding was a bit too tied 
to features that were deprecated and then removed in java 6 or 7.


What would it mean for them if Maven had a default of Java 7.
Could they not just change the Java setting to 1.4 or 1.3 and still 
run Maven and compile their Websphere apps?


Is it not possible to run Maven in a JRE7 VM and compile code with a 
1.3 compiler?
I think that we have done that in the past where our app was being 
built using 1.5 but we had our Eclipse and Maven running in a 1.6VM.



Ron



Markku

On 11/29/2012 04:55 PM, Ron Wheeler wrote:

Java 7 has been out for almost a year and a half.
Java 6 was released in 2006

What keeps people on old versions for over 8 years(1.5)?

We have tried to keep up with the times and feel that we got a lot 
of performance improvements over time without any pain as we changed 
versions.


There does not seem to be any problem using Maven to compile Java 
version 7. Java 7 certainly runs Maven just fine.


Are we not just talking about changing the default to 7 not forcing 
everyone to use 7 or run their IDE on 7 or am I missing something?
They can still select the compiler that they want if they are not up 
to date.



Ron

On 29/11/2012 9:19 AM, Stephen Connolly wrote:
That is a fair point. And I concur, that until core ups its minimum 
JRE

requirement, compiler shouldn't move past that...

Raises the question should core up to 1.6... I don't see a pressing 
need

yet...

Lambdas are not until 1.8, and we don't do the crazy generics stuff 
that,
for example, forced Jenkins to require 1.6 to build. So without a 
pressing

need, I think core should stay on 1.5 for now


On 29 November 2012 10:39, Jochen Wiedmann 
wrote:


Leaving aside questions of compatibility, Java 7 as compiler 
default would
be a poor choice. After all, that would require JRE 7 as a 
standard for
running Maven, or using one of the Eclipse compilers. Otherwise, 
that would

be unsupported by the compiler.



On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler <
rwhee...@artifact-software.com

wrote:
+1

On 28/11/2012 1:36 PM, Mark Derricutt wrote:


Now that Oracle are controlling Java on OSX we can no longer "blame
Apple" - I'd love to see the default become Java 7 now.

And if one needs to lock down to the older versions, lock them 
down.



On 29/11/2012, at 7:07 AM, Curtis Rueden  wrote:

  Good to know that Maven is now only 8 years behind.

I blame Apple.




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


--**--**- 


To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<

users-unsubscr...@maven.apache.org>

For additional commands, e-mail: users-h...@maven.apache.org




--
The best argument for celibacy is that the clergy will sooner or 
later

become extinct.







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why does mvn compiile using java 1.3?

[Markku Saarela]

People is stuck for old Java versions due to the fact that for example 
organizations are using IBM WebSphere and do not upgrade those 
immediately when new version of WAS is released.  WAS 6.1 which was 
released in 2006 and just add support for JDK 1.5 not 1.6. It is WAS 7 
which has JDK 6 support build in from beginning 2008. Just latest WAS 
8.5 has possibility to use JDK 7.


Lot of organizations is still running with WAS 6 .

Markku

On 11/29/2012 04:55 PM, Ron Wheeler wrote:

Java 7 has been out for almost a year and a half.
Java 6 was released in 2006

What keeps people on old versions for over 8 years(1.5)?

We have tried to keep up with the times and feel that we got a lot of 
performance improvements over time without any pain as we changed 
versions.


There does not seem to be any problem using Maven to compile Java 
version 7. Java 7 certainly runs Maven just fine.


Are we not just talking about changing the default to 7 not forcing 
everyone to use 7 or run their IDE on 7 or am I missing something?
They can still select the compiler that they want if they are not up 
to date.



Ron

On 29/11/2012 9:19 AM, Stephen Connolly wrote:

That is a fair point. And I concur, that until core ups its minimum JRE
requirement, compiler shouldn't move past that...

Raises the question should core up to 1.6... I don't see a pressing need
yet...

Lambdas are not until 1.8, and we don't do the crazy generics stuff 
that,
for example, forced Jenkins to require 1.6 to build. So without a 
pressing

need, I think core should stay on 1.5 for now


On 29 November 2012 10:39, Jochen Wiedmann 
wrote:


Leaving aside questions of compatibility, Java 7 as compiler default 
would

be a poor choice. After all, that would require JRE 7 as a standard for
running Maven, or using one of the Eclipse compilers. Otherwise, 
that would

be unsupported by the compiler.



On Wed, Nov 28, 2012 at 8:43 PM, Ron Wheeler <
rwhee...@artifact-software.com

wrote:
+1

On 28/11/2012 1:36 PM, Mark Derricutt wrote:


Now that Oracle are controlling Java on OSX we can no longer "blame
Apple" - I'd love to see the default become Java 7 now.

And if one needs to lock down to the older versions, lock them down.


On 29/11/2012, at 7:07 AM, Curtis Rueden  wrote:

  Good to know that Maven is now only 8 years behind.

I blame Apple.




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


--**--**- 


To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<

users-unsubscr...@maven.apache.org>

For additional commands, e-mail: users-h...@maven.apache.org




--
The best argument for celibacy is that the clergy will sooner or later
become extinct.







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: DAO injection in integration tests with a few database server specific methods

[Markku Saarela]

Not on this list, this is for Maven.

Markku
On 11/24/2012 08:28 PM, Martin Gainty wrote:

so.. i guess the short answer is no there is no way to introduce hints into 
Hibernate generated queries.. Takk,
Martin__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.

  > Date: Sat, 24 Nov 2012 19:42:49 +0200

From: markku.saar...@iki.fi
To: users@maven.apache.org
Subject: Re: DAO injection in integration tests with a few database server 
specific methods

Use Spring and Hibernate list for questions related on those.

Markku

On 11/24/2012 05:36 PM, Martin Gainty wrote:

that *should* work as Hibernate Session would generate an List of Persisted 
NavbarLanguage Classes (which your method returns) ..but...the generated Query 
would not be hinted..so optimizing the query is not enabled
does anyone know to introduce Hints into Hibernate generated queries?
Martin
__
Place long winded disclaimer here > Date: Fri, 23 Nov 2012 01:55:57 -0800

From: mittiprove...@yahoo.se
To: users@maven.apache.org
Subject: Re: DAO injection in integration tests with a few database server 
specific methods

Here is how I'm using the injected custom DAO bean method:

public List findWithNavbar(Navbar navbar) {
if (navbarLanguageCustomDao != null) {
return navbarLanguageCustomDao.findWithNavbar(navbar);
} else {
Criteria criteria = 
getSession().createCriteria(getPersistentClass());
criteria.add(Restrictions.eq("navbar",
navbar)).addOrder(Order.asc("languageCode"));
return criteria.list();
}
}

Not sure if it's the best way to go though :-)



--
View this message in context: 
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods-tp5732576p5732611.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: DAO injection in integration tests with a few database server specific methods

[Markku Saarela]

Use Spring and Hibernate list for questions related on those.

Markku

On 11/24/2012 05:36 PM, Martin Gainty wrote:

that *should* work as Hibernate Session would generate an List of Persisted 
NavbarLanguage Classes (which your method returns) ..but...the generated Query 
would not be hinted..so optimizing the query is not enabled
does anyone know to introduce Hints into Hibernate generated queries?
Martin
__
Place long winded disclaimer here > Date: Fri, 23 Nov 2012 01:55:57 -0800

From: mittiprove...@yahoo.se
To: users@maven.apache.org
Subject: Re: DAO injection in integration tests with a few database server 
specific methods

Here is how I'm using the injected custom DAO bean method:

public List findWithNavbar(Navbar navbar) {
if (navbarLanguageCustomDao != null) {
return navbarLanguageCustomDao.findWithNavbar(navbar);
} else {
Criteria criteria = 
getSession().createCriteria(getPersistentClass());
criteria.add(Restrictions.eq("navbar",
navbar)).addOrder(Order.asc("languageCode"));
return criteria.list();
}
}

Not sure if it's the best way to go though :-)



--
View this message in context: 
http://maven.40175.n5.nabble.com/DAO-injection-in-integration-tests-with-a-few-database-server-specific-methods-tp5732576p5732611.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: can I run mvn install with no verify phase?

[Markku Saarela]

Read also Maven books from this site:

http://www.sonatype.com/Support/Books

rgds,

Markku

On 10/06/2012 06:42 PM, Rob Withers wrote:

Thanks for your help.  I did some O'Reilly reading.   I could not find that
I could skip the verify, but as Robert mentioned I can control the threshold
of the plugins.

I now have:
workspace/
 pom.xml
 murmur-events/
 pom.xml
 murmur-utils/
 pom.xml
 reed-solomon/
 pom.xml
 murmur/
 pom.xml
 genesis/
 pom.xml

where the reed-solomon overrides the plugin values for the analysis tools.

It is fairly complicated to setup each new project, since I need to combine
maven3, git, eclipse, and a Jenkins project for each one.  I had to generate
the top and put it into the Jenkins repository, which is separate than the
.m2 repository, but it works.  I may switch to a public repository at some
point.  Anyways, once I get each project setup, it is gravy.

Thanks,
Rob


From: Barrie Treloar [mailto:baerr...@gmail.com]

On Sat, Oct 6, 2012 at 8:14 PM, Rob Withers  wrote:

As the subject asks: can I run mvn install with a no verify flag to
skip the verify phase?

Rob, please read the maven books.
Your questions are showing you need to grasp the basics first.
You will save yourself lots of pain.



From: Robert Scholte [mailto:rfscho...@apache.org]

Can you reach the age of 100 without ever being 99?

You must find your solution in the plugin bound to the verify-phase.
A strategy could be to make add a profile with the ITs.

run-its


If you want it to be executed by default, add this kind of activation:

  
skipTests
!true
  

So mvn install -DskipTests=true will indeed skip the tests

Otherwise activate it by id (that is: -Prun-its)

Robert

On Sat, 06 Oct 2012 12:44:36 +0200 Rob Withers 
wrote:


As the subject asks: can I run mvn install with a no verify flag to
skip the verify phase?


Thanks,

Rob

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [PATCH provided] How to generate an announcement from GitHub with Changes plugin?

[Markku Saarela]

Hi

Created issue MCHANGES-290 
<http://jira.codehaus.org/browse/MCHANGES-290> and patch is applied.


Markku

On 09/30/2012 08:43 AM, Markku Saarela wrote:

Hi,

Thanks, i'll look those.

Markku

On 09/30/2012 12:06 AM, Dennis Lundberg wrote:

Hi

Support for a report based on issues at GitHub was added in the latest
version. There is no support for announcements yet. It should be
relatively easy to do though, now that the code to fetch issues from the
GitHub issue tracker is in place.

Patches are welcome. Have a look in AnnouncementMojo how it has been
implemented for JIRA and Trac.

On 2012-09-29 10:22, Markku Saarela wrote:

Hi,

Is it possible somehow to generate an announcement from GitHub with
Changes plugin.

Or is there an other way?

Rgds, Markku

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to generate an announcement from GitHub with Changes plugin?

[Markku Saarela]

Hi,

Thanks, i'll look those.

Markku

On 09/30/2012 12:06 AM, Dennis Lundberg wrote:

Hi

Support for a report based on issues at GitHub was added in the latest
version. There is no support for announcements yet. It should be
relatively easy to do though, now that the code to fetch issues from the
GitHub issue tracker is in place.

Patches are welcome. Have a look in AnnouncementMojo how it has been
implemented for JIRA and Trac.

On 2012-09-29 10:22, Markku Saarela wrote:

Hi,

Is it possible somehow to generate an announcement from GitHub with
Changes plugin.

Or is there an other way?

Rgds, Markku

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

How to generate an announcement from GitHub with Changes plugin?

[Markku Saarela]

Hi,

Is it possible somehow to generate an announcement from GitHub with 
Changes plugin.


Or is there an other way?

Rgds, Markku

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Ear Plugin skinnyWars EJB problem

[Markku Saarela]

In that case WAR Overlays[1] come into picture.

Markku

[1] http://maven.apache.org/plugins/maven-war-plugin/overlays.html

On 09/25/2012 05:57 PM, nskmda wrote:

Well, okay, I read that instruction.

But I may also need to have a WAR artifact including all dependent EJBs in
case I want to deploy it as WAR only, no EAR.

In this case I still need to preserve original WAR dependencies.
And I need m-ear-p to strip them if they're a listed as EAR dependencies
(when I configure m-ear-p to produce "skinnyWar" modules).

This doesn't really work.
Whatever jar dependencies I have in my EAR artifact get
stripped from the WAR.

But no ejb EAR dependencies get stripped from WAR.
And I can't do a jar on them because I will loose the
 capability (to generate proper application.xml).

I guess, there was something in mind when making m-ear-p to skip those
ejb dependencies when stripping down WAR artifact.



--
View this message in context: 
http://maven.40175.n5.nabble.com/Ear-Plugin-skinnyWars-EJB-problem-tp563p5723616.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[SOLVED]: Maven plugin configuration properties in execution element not working.

[Markku Saarela]

Hi,

It seems to be impossible to have multiple execution configuration for 
direct cli plugin invocation.


So i refactored plugin that now it can invoke directly from cli with 
multiple configurations.


Markku

On 09/17/2012 11:30 AM, Markku Saarela wrote:

Hi,

I have problem with plugin developed by myself.

I have just figured out that the problem is with executionIds when 
running from command line.


It get default-cli as execution id and not found configuration from 
other execution id.


I just try to figure out how you can have different executionIds and 
get them properly configured.


Markku

On 09/17/2012 11:22 AM, Baptiste MATHUS wrote:

Sorry Markku, but I'm not sure I understand what you want. You have a
problem using a plugin you developed?
The best thing is to post at least an excerpt of that POM part, the
problematic one, so that we can have a look.

Even better would be having a test project posted somewhere.

Cheers

2012/9/17 Markku Saarela 


Hi,

I made Maven plugin and it's parameter configuration is working plugin
element but notin execution elements. Maven reports parameters are 
missing

or invalid.

So how to get execution configuration working?

rgds,

Markku

--**--**- 

To unsubscribe, e-mail: 
users-unsubscribe@maven.**apache.org

For additional commands, e-mail: users-h...@maven.apache.org

--
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
nbsp;!
  



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven plugin configuration properties in execution element not working.

[Markku Saarela]

Hi,

I have problem with plugin developed by myself.

I have just figured out that the problem is with executionIds when 
running from command line.


It get default-cli as execution id and not found configuration from 
other execution id.


I just try to figure out how you can have different executionIds and get 
them properly configured.


Markku

On 09/17/2012 11:22 AM, Baptiste MATHUS wrote:

Sorry Markku, but I'm not sure I understand what you want. You have a
problem using a plugin you developed?
The best thing is to post at least an excerpt of that POM part, the
problematic one, so that we can have a look.

Even better would be having a test project posted somewhere.

Cheers

2012/9/17 Markku Saarela 


Hi,

I made Maven plugin and it's parameter configuration is working plugin
element but notin execution elements. Maven reports parameters are missing
or invalid.

So how to get execution configuration working?

rgds,

Markku

--**--**-
To unsubscribe, e-mail: 
users-unsubscribe@maven.**apache.org
For additional commands, e-mail: users-h...@maven.apache.org

--
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
nbsp;!
  



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven plugin configuration properties in execution element not working.

[Markku Saarela]

Hi,

I made Maven plugin and it's parameter configuration is working plugin 
element but notin execution elements. Maven reports parameters are 
missing or invalid.


So how to get execution configuration working?

rgds,

Markku

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: (java.net.SocketException) caught when connecting to the target host: Invalid argument: connect

[Markku Saarela]

On Windows networking if you have many network adapters like WLAN, VPN, 
LAN etc. disabling one adapter migh be not enought. The you could 
disable IPv6 permanently on all adapters.  Here is instructions how do that:


http://www.addictivetips.com/windows-tips/how-to-disable-ipv6-in-windows-7/

Markku

On 5.8.2012 3:58, Gary White wrote:

I spoke too soon.  I disabled IPv6 on my network adapter and it didn't fix
the problem.  After I sent the previous email, I decided to try the VM arg
and it did the trick.  I'm curious as to why one worked and the other
didn't.

Thanks again,
Gary

-Original Message-
From: Gary White [mailto:gary_wh...@verizon.net]
Sent: Saturday, August 04, 2012 8:36 PM
To: 'Maven Users List'
Subject: RE: (java.net.SocketException) caught when connecting to the target
host: Invalid argument: connect
Markku,

Your suggestion sounded promising but unfortunately didn't resolve the
problem.

Thanks anyway.

Gary

-----Original Message-
From: Markku Saarela [mailto:markku.saar...@pp6.inet.fi]
Sent: Saturday, August 04, 2012 5:01 AM
To: users@maven.apache.org
Subject: Re: (java.net.SocketException) caught when connecting to the target
host: Invalid argument: connect

Hi,

You probably hit IPv4 vs IPv6 incompatibility.  JDK 7 uses IPv6 by default
to connect (if OS and network adapter supports it).

Try run Java with this VM argument -Djava.net.preferIPv4Stack=true or try to
set your network adapted only use IPv4 .

Markku

On 3.8.2012 16:22, Gary White wrote:

I encountered the above error (more complete listing at end of
email/post) on a new Windows 7 64 bit machine that I'm in the process
of setting up.  I originally encountered problems running mvn against
a few projects that I had moved from an XP machine and decided to
troubleshoot using the following basic command from Maven By Example
that

is used to create a simple project:
   


mvn archetype:generate -DgroupId=org.sonatype.mavenbook.simple
-DartifactId=simple -Dpackage=org.sonatype -Dversion=1.0-SNAPSHOT

   


I've tried this with both the 32 & 64 bit versions of JDK 7u5.  I
tried Maven versions 2.2.1, 3.0.3 and 3.0.4 (output below is from
3.0.4).  I've also tried it with Windows Firewall completely disabled
and AV completely removed.  I'm connected via Verizon FIOS with the

default router setup.

Maven works fine on the other XP machine on the same network.

   


Any help is greatly appreciated.

Gary

   


Truncated output follows (I can send complete output if necessary);
note - the error repeats for each of the following plugins:

org.apache.maven.plugins:maven-clean-plugin:2.4.1

org.apache.maven.plugins:maven-install-plugin:2.3.1

org.apache.maven.plugins:maven-deploy-plugin:2.7

org.apache.maven.plugins:maven-site-plugin:3.0

org.apache.maven.plugins:maven-antrun-plugin:1.3

org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5

org.apache.maven.plugins:maven-dependency-plugin:2.1

org.apache.maven.plugins:maven-release-plugin:2.0

   


Output:

   


C:\workspace\ch-simple>mvn archetype:generate
-DgroupId=org.sonatype.mavenbook.simple -DartifactId=simple
-Dpackage=org.sonatype -Dversion=1.0-SNAPSHOT -e -X

Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)

Maven home: C:\Tools\apache-maven

Java version: 1.7.0_05, vendor: Oracle Corporation

Java home: C:\Program Files (x86)\Java\jdk1.7.0_05\jre

Default locale: en_US, platform encoding: Cp1252

OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"

[INFO] Error stacktraces are turned on.

[DEBUG] Reading global settings from
C:\Tools\apache-maven\conf\settings.xml

[DEBUG] Reading user settings from C:\Users\Gary\.m2\settings.xml

[DEBUG] Using local repository at C:\Users\Gary\.m2\repository

[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10
for C:\Users\Gary\.m2\repository

[INFO] Scanning for projects...

[DEBUG] Extension realms for project

org.apache.maven:standalone-pom:pom:1:

(none)

[DEBUG] Looking up lifecyle mappings for packaging pom from
ClassRealm[plexus.core, parent: null]

[DEBUG] Resolving plugin prefix archetype from
[org.apache.maven.plugins, org.codehaus.mojo]

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://repo.maven.apache.org/maven2

Downloading:
http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-cle
an-plu gin/2.4.1/maven-clean-plugin-2.4.1.pom

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRe
questD
irector tryConnect

INFO: I/O exception (java.net.SocketException) caught when connecting
to the target host: Invalid argument: connect

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRe
questD
irector tryConnect

INFO: Retrying connect

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRe
questD
irector tryConnect

Re: (java.net.SocketException) caught when connecting to the target host: Invalid argument: connect

[Markku Saarela]

Hi,

You probably hit IPv4 vs IPv6 incompatibility.  JDK 7 uses IPv6 by 
default to connect (if OS and network adapter supports it).


Try run Java with this VM argument -Djava.net.preferIPv4Stack=true or 
try to set your network adapted only use IPv4 .


Markku

On 3.8.2012 16:22, Gary White wrote:

I encountered the above error (more complete listing at end of email/post)
on a new Windows 7 64 bit machine that I'm in the process of setting up.  I
originally encountered problems running mvn against a few projects that I
had moved from an XP machine and decided to troubleshoot using the following
basic command from Maven By Example that is used to create a simple project:

  


mvn archetype:generate -DgroupId=org.sonatype.mavenbook.simple
-DartifactId=simple -Dpackage=org.sonatype -Dversion=1.0-SNAPSHOT

  


I've tried this with both the 32 & 64 bit versions of JDK 7u5.  I tried
Maven versions 2.2.1, 3.0.3 and 3.0.4 (output below is from 3.0.4).  I've
also tried it with Windows Firewall completely disabled and AV completely
removed.  I'm connected via Verizon FIOS with the default router setup.
Maven works fine on the other XP machine on the same network.

  


Any help is greatly appreciated.

Gary

  


Truncated output follows (I can send complete output if necessary); note -
the error repeats for each of the following plugins:

org.apache.maven.plugins:maven-clean-plugin:2.4.1

org.apache.maven.plugins:maven-install-plugin:2.3.1

org.apache.maven.plugins:maven-deploy-plugin:2.7

org.apache.maven.plugins:maven-site-plugin:3.0

org.apache.maven.plugins:maven-antrun-plugin:1.3

org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5

org.apache.maven.plugins:maven-dependency-plugin:2.1

org.apache.maven.plugins:maven-release-plugin:2.0

  


Output:

  


C:\workspace\ch-simple>mvn archetype:generate
-DgroupId=org.sonatype.mavenbook.simple -DartifactId=simple
-Dpackage=org.sonatype -Dversion=1.0-SNAPSHOT -e -X

Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)

Maven home: C:\Tools\apache-maven

Java version: 1.7.0_05, vendor: Oracle Corporation

Java home: C:\Program Files (x86)\Java\jdk1.7.0_05\jre

Default locale: en_US, platform encoding: Cp1252

OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"

[INFO] Error stacktraces are turned on.

[DEBUG] Reading global settings from C:\Tools\apache-maven\conf\settings.xml

[DEBUG] Reading user settings from C:\Users\Gary\.m2\settings.xml

[DEBUG] Using local repository at C:\Users\Gary\.m2\repository

[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
C:\Users\Gary\.m2\repository

[INFO] Scanning for projects...

[DEBUG] Extension realms for project org.apache.maven:standalone-pom:pom:1:
(none)

[DEBUG] Looking up lifecyle mappings for packaging pom from
ClassRealm[plexus.core, parent: null]

[DEBUG] Resolving plugin prefix archetype from [org.apache.maven.plugins,
org.codehaus.mojo]

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://repo.maven.apache.org/maven2

Downloading:
http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plu
gin/2.4.1/maven-clean-plugin-2.4.1.pom

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestD
irector tryConnect

INFO: I/O exception (java.net.SocketException) caught when connecting to the
target host: Invalid argument: connect

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestD
irector tryConnect

INFO: Retrying connect

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestD
irector tryConnect

INFO: I/O exception (java.net.SocketException) caught when connecting to the
target host: Invalid argument: connect

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestD
irector tryConnect

INFO: Retrying connect

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestD
irector tryConnect

INFO: I/O exception (java.net.SocketException) caught when connecting to the
target host: Invalid argument: connect

Aug 03, 2012 8:00:44 AM
org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestD
irector tryConnect

INFO: Retrying connect

[DEBUG] Writing resolution tracking file
C:\Users\Gary\.m2\repository\org\apache\maven\plugins\maven-clean-plugin\2.4
.1\maven-clean-plugin-2.4.1.pom.lastUpdated

[WARNING] Failed to retrieve plugin descriptor for
org.apache.maven.plugins:maven-clean-plugin:2.4.1: Plugin
org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for
org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1

org.apache.maven.plugin.PluginResolutionException: Plugin
org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies
could not be resolved: Failed to read artifact descriptor for
org.apache.maven

Re: Maven with JDK 7

[Markku Saarela]

Hi,

If you have already turn of firewall, go to network adapter properties 
and disable IPv6 support.


Markku

On 27.6.2012 15:26, Markku Saarela wrote:

Hi,

Java 7 use IPv6 (not IPv4) if OS supports it. So if you firewall 
restricts IPv6 then you got behavior you describe. Also Nexus running 
on Java 7 failed to connect and app servers etc if firewall does not 
allow IPv6 communication.


Markku

On 27.6.2012 15:18, Delaney, Andy wrote:


Hi All

I’m working on a JDK 7 project and am trying to use maven to build 
the project.   However, when I try to run the maven bat under Java 7 
it fails to download any dependencies – when I switch back to Java 6 
it downloads them just fine but of course can’t compile my java 7 
sources.


Looking through the forums the only advice I can get is to revert to 
Java 6 – this isn’t an option as I need to compile Java 7 sources.


Has anyone come across this problem or understand why it is happening 
– presumably there is a change in the JDK and the way it handles 
socket connections?


The underlying exception is a timeout exception which would lead me 
think this was something to do with proxies or firewalls but I have 
tried switching the firewall off and as it runs OK under JDK 6 so I 
don’t think that’s it.


Caused by: java.net.ConnectException: Connection timed out: connect

at java.net.DualStackPlainSocketImpl.connect0(Native Method)

at 
java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:69)


at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)


at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)


at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)


at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)

at java.net.Socket.connect(Socket.java:579)

at 
org.apache.maven.wagon.providers.http.httpclient.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)


at 
org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)


... 16 more

I would appreciate any help you might be able to offer me.

Many thanks

Andy

Tullett Prebon - Best Data Provider (Broker) - Inside Market Data 
Awards 2012


---

The information contained in this email is confidential and may also 
contain privileged information. Sender does not waive confidentiality 
or legal privilege. If you are not the intended recipient please 
notify the sender immediately; you should not retain this message or 
disclose its content to anyone.


Internet communications are not secure or error free and the sender 
does not accept any liability for the content of the email. Although 
emails are routinely screened for viruses, the sender does not accept 
responsibility for any damage caused. Replies to this email may be 
monitored.


For more information about the Tullett Prebon group of companies 
please visit the following web site: _www.tullettprebon.com_


---









-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven with JDK 7

[Markku Saarela]

Hi,

Java 7 use IPv6 (not IPv4) if OS supports it. So if you firewall 
restricts IPv6 then you got behavior you describe. Also Nexus running on 
Java 7 failed to connect and app servers etc if firewall does not allow 
IPv6 communication.


Markku

On 27.6.2012 15:18, Delaney, Andy wrote:


Hi All

I’m working on a JDK 7 project and am trying to use maven to build the 
project.   However, when I try to run the maven bat under Java 7 it 
fails to download any dependencies – when I switch back to Java 6 it 
downloads them just fine but of course can’t compile my java 7 sources.


Looking through the forums the only advice I can get is to revert to 
Java 6 – this isn’t an option as I need to compile Java 7 sources.


Has anyone come across this problem or understand why it is happening 
– presumably there is a change in the JDK and the way it handles 
socket connections?


The underlying exception is a timeout exception which would lead me 
think this was something to do with proxies or firewalls but I have 
tried switching the firewall off and as it runs OK under JDK 6 so I 
don’t think that’s it.


Caused by: java.net.ConnectException: Connection timed out: connect

at java.net.DualStackPlainSocketImpl.connect0(Native Method)

at 
java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:69)


at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)


at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)


at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)


at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)

at java.net.Socket.connect(Socket.java:579)

at 
org.apache.maven.wagon.providers.http.httpclient.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)


at 
org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148)


... 16 more

I would appreciate any help you might be able to offer me.

Many thanks

Andy

Tullett Prebon - Best Data Provider (Broker) - Inside Market Data 
Awards 2012


---

The information contained in this email is confidential and may also 
contain privileged information. Sender does not waive confidentiality 
or legal privilege. If you are not the intended recipient please 
notify the sender immediately; you should not retain this message or 
disclose its content to anyone.


Internet communications are not secure or error free and the sender 
does not accept any liability for the content of the email. Although 
emails are routinely screened for viruses, the sender does not accept 
responsibility for any damage caused. Replies to this email may be 
monitored.


For more information about the Tullett Prebon group of companies 
please visit the following web site: _www.tullettprebon.com_


---

Re: The Maven Way

[Markku Saarela]

Hi,

I recommend two "books" from Sonatype, Maven by Example 1) and Maven 
Cookbook 2)


1) http://www.sonatype.com/index.php/Support/Books/Maven-By-Example
2) http://www.sonatype.com/index.php/Support/Books/The-Maven-Cookbook

Markku
On 17.4.2012 16:55, Wolf Geldmacher wrote:

Hi list,

a simple question with (hopefully) a simple answer:

Is there some coherent documentation of "the Maven way"?

I'm *not* looking for:
* documentation of the Maven syntax
* documentation of Maven plugins
* Maven reference documentation
* "Use the Source, Luke!" style of advice

What I'm looking for is:
* a collection of patterns / anti-patterns in the use of Maven,
* documentation on the "Do's and Dont's" when using Maven,
* documentation of the best practices implemented by Maven,
* documentation of basic assumptions in Maven.

I'm being bitten by gotcha's that spring up at inconvenient times
and *then* being told that I've strayed from "The Way"; I'd rather
follow some road signs upfront than find myself confronted with
scathing dogs in some lonely backyard that I happen to stumble into.

Something along the lines of Chapter 3.6 of "Maven: The Complete
Reference", which sets out to "... distill some of this knowledge to
help you adopt best practices from the start without having to wade
through years of discussions ..." but then, unfortunately, only covers
two (Dependency Grouping and Multi-module vs. Inheritance).
Similar to this, just much more complete and with some
background/rationale thrown in, if possible.

Pointers anyone?

Pretty please?

Regards,
Wolf


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Getting Error in Maven

[Markku Saarela]

You are using  native2ascii-maven-plugin:1.0-alpha-1 with Java version: 
1.7.0 and 1.0-alpha-1 version of plugin is not compatible with JDK 7.


So you either upgrade plugin to version 1.0-beta-1 or run Maven with JDK 6

Markku

On 30.3.2012 16:39, debashish mukherjee wrote:

Hi,

I am using maven 3.0.4 on my windows 7 machine, while running mvn
jetty:run, I am facing these errors, please provide with some solution.

Apache Maven 3.0.4 (r1232337; 2012-01-17 14:14:56+0530)
Maven home: D:\softwares\apache-maven-3.0.4
Java version: 1.7.0, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from
D:\softwares\apache-maven-3.0.4\conf\settings.xml
[DEBUG] Reading user settings from C:\Users\deb\.m2\settings.xml
[DEBUG] Using local repository at C:\Users\deb\.m2\repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
C:\Users\deb\.m2\repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project
com.mycompany:myproject:war:1.0-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging war from
ClassRealm[plexus.core, parent: null]
[DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix jetty to
org.mortbay.jetty:maven-jetty-plugin from POM
com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] === REACTOR BUILD PLAN

[DEBUG] Project: com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] Tasks:   [jetty:run]
[DEBUG] Style:   Regular
[DEBUG]
===
[INFO]

[INFO]

[INFO] Building AppFuse Struts 2 Application 1.0-SNAPSHOT
[INFO]

[DEBUG] Resolving plugin prefix jetty from [org.apache.maven.plugins,
org.codehaus.mojo]
[DEBUG] Resolved plugin prefix jetty to
org.mortbay.jetty:maven-jetty-plugin from POM
com.mycompany:myproject:war:1.0-SNAPSHOT
[DEBUG] Lifecycle default ->  [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean ->  [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site ->  [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default ->  [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean ->  [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site ->  [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default ->  [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean ->  [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site ->  [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN

[DEBUG] Project:   com.mycompany:myproject:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [runtime]
[DEBUG] Repositories (dependencies): [appfuse-snapshots (
http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots),
central (http://repo.maven.apache.org/maven2, releases)]
[DEBUG] Repositories (plugins) : [appfuse-snapshots (
http://oss.sonatype.org/content/repositories/appfuse-snapshots, snapshots),
central (http://repo.maven.apache.org/maven2, releases)]
[DEBUG] --- init fork of com.mycompany:myproject:1.0-SNAPSHOT for
org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) ---
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [compile, test]
[DEBUG]
---
[DEBUG] Goal:
  org.codehaus.mojo:native2ascii-maven-plugin:1.0-alpha-1:native2ascii
(native2ascii-utf8)
[DEBUG] Style: Regular
[DEBUG] Configuration:

   target/resources
   UTF8
   ApplicationResources.properties,
 ApplicationResources_de

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

Our releases do not have any configuration files in artifact's, instead 
manifest classpaths has directory name to point directory that has those 
files. We use separate build to assembly different configurations into 
different environments putting configurations in place.


I like to use Eclipse ability to hot deploy modifications of code into 
server while debugging development trunk code.


So what you say and my experience it is impossible to use multi-module 
project imported with project references for developing software with 
hot deployment and also unit testing without having profiles to set 
resource directories for Eclipse unit testing and deploying into server.


It's not so convenient to go outside IDE to deploy artifact into server 
in order to debug / test modifications made.


Markku

On 2.3.2012 21:29, Ron Wheeler wrote:
I am not sure if this directly answers your question but perhaps a bit 
of background helps.


We use Eclipse STS which comes with Maven support built in. We used to 
waste so much time upgrading Eclipse and getting everyone configured 
in the same way.
Now it is a single download (BIG) to get everything that you need 
except Subversion.


We have individual projects since the project is divided up on 
functional lines with core modules for the database access and some 
modules that can best be described as utilities (messaging for example).
This means that for any maintenance activity almost all of the modules 
are not affected.

In addition, modules are worked on by different people.
No one would have all of modules checked out at once. Certainly you 
would not have them open in Eclipse.


We use SNAPSHOTs during development and maintenance.
We do not make all of the 70 modules carry the same release version. 
It is possible to see a version 1.10.3 of the overall application 
running with most of the WAR files as version 1.10 if they were bug 
free up to the 1.10.3 release.


We do some unit testing and do most of our testing on the developer's 
workstation.
We have at least 1 test server where developers can test in an 
environment that is almost identical to production and can be tested 
by the client(s). More than 1 if we have a big maintenance issue while 
we are trying to get a major development tested. We are starting to 
use the cloud for this so the actual number of test servers 
potentially available is close to infinite.


We deploy the WAR files by hand to the appropriate server.

We use JNDI to support our Spring configurations so we do not have any 
variation in the WARs between test and different production servers.


This is certainly not the only way to do things but I have never heard 
of any problems with test classes or test configurations leaking into 
production.


The build is described in the master POM for the project. The master 
POM is the key to every project and contains everything that is common 
between modules so the module poms are pretty small.


Below is the build description from the master POM for a project.
I hope that this helps a bit.

Ron


src/main
src/main/scripts
src/test
target/classes
target/test-classes


src/main

**/*.java





test

**/*.java



target


org.apache.maven.plugins
maven-compiler-plugin
2.3.2

UTF-8
1.6
1.6



org.apache.maven.plugins
maven-resources-plugin
2.5

UTF-8



org.apache.maven.plugins
maven-war-plugin
2.2

WebContent


true
true





org.apache.maven.plugins
maven-jar-plugin
2.4



true
true









org.apache.maven.plugins
maven-assembly-plugin
2.3


package

single




true
true




jar-with-dependencies












Ron


On 02/03/2012 2:00 PM, Markku Saarela wrote:
In multi-module project i hit the same problem with m2e and 
maven-eclipse-plugin. Are you saying not to import multi-module 
projects into Eclipse, instead every module separately? Or you don't 
use server plugins to deploy application instead you deploy outside 
Eclipse and use remote application debugging? But still this does not 
prevent unit tests failing with multi-module configuration because of 
this dependent project classpath has those artifacts in it's 
classpath before it's own ones.


So if you have solution to this i am more than happy to hear it.

Markku

On 2.3.2012 17:50, Ron Wheeler wrote:
We have been developing and maintaining a large  portal application 
with over 70 WAR files in Eclipse with Maven since 2007 and several 
smaller portals and standalone applications. We have not had this 
problem.


That is not to say that I am an expert in Eclipse but we know enough 
to make it work.


We do not use maven-eclipse-plug-in. We use the assembly plug-in to 
build our war files.

Perhaps that is the difference.

We also deploy to Tomcat which might be a better servlet engine than 
Glassfish.


I am not sure how relevant our experience is to your problem but if 
I can provide any additional information that you think might help, 
let me know.

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

In multi-module project i hit the same problem with m2e and 
maven-eclipse-plugin. Are you saying not to import multi-module projects 
into Eclipse, instead every module separately? Or you don't use server 
plugins to deploy application instead you deploy outside Eclipse and use 
remote application debugging? But still this does not prevent unit tests 
failing with multi-module configuration because of this dependent 
project classpath has those artifacts in it's classpath before it's own 
ones.


So if you have solution to this i am more than happy to hear it.

Markku

On 2.3.2012 17:50, Ron Wheeler wrote:
We have been developing and maintaining a large  portal application 
with over 70 WAR files in Eclipse with Maven since 2007 and several 
smaller portals and standalone applications. We have not had this 
problem.


That is not to say that I am an expert in Eclipse but we know enough 
to make it work.


We do not use maven-eclipse-plug-in. We use the assembly plug-in to 
build our war files.

Perhaps that is the difference.

We also deploy to Tomcat which might be a better servlet engine than 
Glassfish.


I am not sure how relevant our experience is to your problem but if I 
can provide any additional information that you think might help, let 
me know.


Ron


On 02/03/2012 10:19 AM, Markku Saarela wrote:

Hi,

You don't understand how Eclipse IDE works. Eclipse does not have 
different classpaths for testing and actual runtime. So Eclipse basic 
design is faulty. There is bug open since 2008 to provide means to 
tell Eclipse that which are test sources and not include them to 
runtime classpath. https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708


So everything under src/test goes also into GlassFish server if you 
deploy application in Eclipse. That causes that those unit test 
properties and configuration and classes are picked first and they 
are effective and application does not work.


Even worst if you have multi-module project and B module is dependent 
from A and A project defines SPI interface and has in src/test/java 
test implementation for that and of course in 
src/test/resources/META-INF/services SPI file for exposing that test 
SPI implementation then if B implements also that SPI interface and 
put SPI file in src/main/resources/META-INF/services, you cannot test 
you implementation via ServiceLoader because it pick's that module A 
test implementation. Same goes for properties and everything else.


Of course NetBeans and IntelliJ has correct way to do things but they 
are not an option.


Markku


On 2.3.2012 15:15, Ron Wheeler wrote:

On 02/03/2012 1:32 AM, Markku Saarela wrote:

Hi,

Developing with Eclipse IDE and JavaEE server using 
maven-eclipse-plugin you have to use profiles, because Eclipse does 
not isolate test code and test resources.

Eclipse does
/src/main/   code
/src/test   ... test code and resources

You need to set your maven properly but it works fine unless I don't 
understand your issue.




Only way to do it what i have figured out is to have two profiles 
one for running application in app server and another for unit 
testing same code.  Those profiles has only resources and 
testResources definitions.


Separating test code for separate code is not an option, because 
then Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and 
then a separate
pom for each site that depends on this with overlays to add the 
extra

configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for 
a user to
flaten a maven build deployment, but this is a bad practice and 
it is better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package 
can do.

They are not particularly concerned about "Best Practices".

The most common usage is often left out of the documentation since 
it is "dull" or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple "Best Practice" that most people use, is hard to 
find in the documentation while an obscure "Worst Practice" is 
described because it shows how clever the software developers are 
and how powerful the product is.


There should be a "Best Practice" section on the Maven site 
describing the best way to implement 

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

Hi,

You don't understand how Eclipse IDE works. Eclipse does not have 
different classpaths for testing and actual runtime. So Eclipse basic 
design is faulty. There is bug open since 2008 to provide means to tell 
Eclipse that which are test sources and not include them to runtime 
classpath. https://bugs.eclipse.org/bugs/show_bug.cgi?id=224708


So everything under src/test goes also into GlassFish server if you 
deploy application in Eclipse. That causes that those unit test 
properties and configuration and classes are picked first and they are 
effective and application does not work.


Even worst if you have multi-module project and B module is dependent 
from A and A project defines SPI interface and has in src/test/java test 
implementation for that and of course in 
src/test/resources/META-INF/services SPI file for exposing that test SPI 
implementation then if B implements also that SPI interface and put SPI 
file in src/main/resources/META-INF/services, you cannot test you 
implementation via ServiceLoader because it pick's that module A test 
implementation. Same goes for properties and everything else.


Of course NetBeans and IntelliJ has correct way to do things but they 
are not an option.


Markku


On 2.3.2012 15:15, Ron Wheeler wrote:

On 02/03/2012 1:32 AM, Markku Saarela wrote:

Hi,

Developing with Eclipse IDE and JavaEE server using 
maven-eclipse-plugin you have to use profiles, because Eclipse does 
not isolate test code and test resources.

Eclipse does
/src/main/   code
/src/test   ... test code and resources

You need to set your maven properly but it works fine unless I don't 
understand your issue.




Only way to do it what i have figured out is to have two profiles one 
for running application in app server and another for unit testing 
same code.  Those profiles has only resources and testResources 
definitions.


Separating test code for separate code is not an option, because then 
Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and then 
a separate

pom for each site that depends on this with overlays to add the extra
configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for a 
user to
flaten a maven build deployment, but this is a bad practice and it 
is better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package can do.

They are not particularly concerned about "Best Practices".

The most common usage is often left out of the documentation since 
it is "dull" or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple "Best Practice" that most people use, is hard to 
find in the documentation while an obscure "Worst Practice" is 
described because it shows how clever the software developers are 
and how powerful the product is.


There should be a "Best Practice" section on the Maven site 
describing the best way to implement the common software development 
patterns.


There are not really a lot of cases to consider but every new Maven 
user has to sort out their own case.


Ron



--
View this message in context: 
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528994.html

Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: using build profiles for WAR plugin [maven-eclipse-plugin]

[Markku Saarela]

Hi,

Developing with Eclipse IDE and JavaEE server using maven-eclipse-plugin 
you have to use profiles, because Eclipse does not isolate test code and 
test resources.


Only way to do it what i have figured out is to have two profiles one 
for running application in app server and another for unit testing same 
code.  Those profiles has only resources and testResources definitions.


Separating test code for separate code is not an option, because then 
Sonar reports 0 % coverage.


rgds,

Markku

On 1.3.2012 22:55, Ron Wheeler wrote:

On 01/03/2012 2:43 PM, offbyone wrote:
Ok so I should create a base pom with a war configuration and then a 
separate

pom for each site that depends on this with overlays to add the extra
configuration file.
I will try.

If I am interpreting your comments correctly, profiles allow for a 
user to
flaten a maven build deployment, but this is a bad practice and it is 
better

to make your maven structure deep.

So are profiles going to be deprecated?   I would think I am not 
alone in
getting turned down the wrong path because most of the 
documentation/howtos

I have found point to using profiles.
There are some uses for profiles that seem harmless so it is a 
documentation issue.


It is fairly common in Apache documentation for the programmers to 
make a big deal about all the wonderful things that the package can do.

They are not particularly concerned about "Best Practices".

The most common usage is often left out of the documentation since it 
is "dull" or not very impressive.
This sometimes means that obscure usage of features or seldom used 
features are heavily documented while the main use case is  not 
described.


New Maven users often fall into the trap that you were headed into.

A really simple "Best Practice" that most people use, is hard to find 
in the documentation while an obscure "Worst Practice" is described 
because it shows how clever the software developers are and how 
powerful the product is.


There should be a "Best Practice" section on the Maven site describing 
the best way to implement the common software development patterns.


There are not really a lot of cases to consider but every new Maven 
user has to sort out their own case.


Ron



--
View this message in context: 
http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528994.html

Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Can DITA be used to create site documentation?

[Markku Saarela]

Hi,

You can convert DITA document to the DocBook dokument in to simplified 
dockbook directory descripid here [2] and then configure Doxia to use 
Doxia Simplified DocBook Module [1]


[1] 
http://maven.apache.org/plugins/maven-site-plugin/faq.html#How_to_include_a_custom_Doxia_module_like_Twiki

[2] http://maven.apache.org/doxia/references/index.html

Markku

On 22.9.2011 7:58, Eric Kolotyluk wrote:
I was hoping someone had already tried this and would have some 
examples or tips. I'm not sure I want to pioneer that right now.


Cheers, Eric

On 2011-09-21 9:16 PM, Dan Tran wrote:

why not?  any dita doc can be converted to web online help?  but to
get fancy as a site would be question due to huge effort

-Dan

On Wed, Sep 21, 2011 at 8:06 PM, Eric Kolotyluk
  wrote:
I was wondering if it is possible to use DITA to generate the 
documentation

for a site.

We use DITA for other stuff and it integrates nicely with Eclipse, I 
was

hoping someone might have gone down this route already.

Cheers, Eric

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Adding files to target before creating war

[Markku Saarela]

You can use WAR overlays 
[http://maven.apache.org/plugins/maven-war-plugin/overlays.html] for 
making different war project for different distributions and also 
different EAR projects to match needed WAR project.


rgds,

Markku

On 21.3.2011 17:56, Sam Adams wrote:

We have slightly different configurations that we need to test. For
this very reason we need to build and test different profiles. This
can include different web.xml files so I don't think externalising is
an option in this case.

Thanks,

Sam

On 21 March 2011 15:44, Wendy Smoak  wrote:

On Mon, Mar 21, 2011 at 11:28 AM, Sam Adams  wrote:

This is exactly what I'm trying to do. Why is this not a good idea and
what are the alternatives?

Depends on *why* you're trying to do that, which is why I asked what
problem you're trying to solve.

In general... either externalize the configuration or pack it all
inside and use something that can select the right file so that you
move the exact same war through the (I assume) different environments.

If you build a war for QA, test it, and then build a war for
production and deploy it... what have you *really* tested?

--
Wendy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Adding files to target before creating war

[Markku Saarela]

You can use WAR overlays 
[http://maven.apache.org/plugins/maven-war-plugin/overlays.html] for 
making different war project for different distributions and also 
different EAR projects to match needed WAR project.


rgds,

Markku

On 21.3.2011 17:56, Sam Adams wrote:

We have slightly different configurations that we need to test. For
this very reason we need to build and test different profiles. This
can include different web.xml files so I don't think externalising is
an option in this case.

Thanks,

Sam

On 21 March 2011 15:44, Wendy Smoak  wrote:

On Mon, Mar 21, 2011 at 11:28 AM, Sam Adams  wrote:

This is exactly what I'm trying to do. Why is this not a good idea and
what are the alternatives?

Depends on *why* you're trying to do that, which is why I asked what
problem you're trying to solve.

In general... either externalize the configuration or pack it all
inside and use something that can select the right file so that you
move the exact same war through the (I assume) different environments.

If you build a war for QA, test it, and then build a war for
production and deploy it... what have you *really* tested?

--
Wendy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-metadata-central.xml is missing versions in local repo

[Markku Saarela]

This can be caused by Artifactory if checksums does not match and you 
Artifactory is configured to fail if checksums doesn't match.


Markku

On 22.4.2010 12:53, Florian R. wrote:



Wayne Fay wrote:
   

What MRM are you running -- Nexus, Artifactory, Archiva, etc? Are you
sure this is a problem in Maven and not something related to your MRM?

 

We are running Artifactory 2.2.0.
Maven downloads the files (no HTTP 404s or something like that) and can't
find it afterwards. IMHO this is related to maven.

We partially solved the problem now, it seems the log4j problem was releated
to a parent pom containing a fixed version and that was confusing maven. But
the problem is not reproducable with a simplyfied project using exact this
constellation :(

Does anyone know which fact forces maven to create the
maven-metadata-central.xml to get some idea why this happens?

Florian
   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: mvn release:perform does not honor //servers/server in alternate settings location

[Markku Saarela]

Hi,

Have you tried -gs  /my/alternate/maven2/home/settings.xml (-gs 
--global-settings) ?


mvn -B -gs /my/alternate/maven2/home/settings.xml release:prepare
release:perform

rgds,

Markku

On 21.4.2010 22:36, David Siefert wrote:

On Wed, Apr 21, 2010 at 1:42 PM, David Siefertwrote:

   

Hi All-

I am trying to perform a maven release by invoking the following:

mvn -B -s /my/alternate/maven2/home/settings.xml release:prepare
release:perform

The problem that occurs is during the deploy of the release artifact, it
seems it is not picking up the username/password in
/my/alternate/maven2/home/settings.xml--I get a 401 authentication error.
However, when I place settings.xml in the default location
($HOME/.m2/settings.xml), then the deploy works perfectly.  Does anyone know
how to get around this issue? or is there a newer release of the appropriate
plugin that does not have this problem?

Thanks,
David

 

Ah, found my answer...
mvn -B -s /my/alternate/maven2/home/settings.xml release:prepare
release:perform -Darguments="/my/alternate/maven2/home/settings.xml"

Not very elegant, but works like a charm!

Thanks,
David

   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Accessing resources

[Markku Saarela]

In Eclipse simply add this src/main/resources to Java Build Path as 
source folder then class running in eclipse can see it.


rgds,

Markku

On 6.4.2010 16:39, Benoît Thiébault wrote:

:-)
Sorry that I have not been clear. Let me detail a bit further.

I have a project that I will call MyProjectA. It is structured according to 
Maven conventions:

MyProjectA
|-- pom.xml
`-- src
 |-- main
 |   `-- resources
 |   `-- myImage.png
 |   `-- java
 |   `-- com
 |   `-- mycompany
 |   `-- app
 |   `-- Main.java
 |   `-- ClassRequiringImage.java
 `-- test
 `-- java
 `-- com
 `-- mycompany
 `-- app
 `-- MainTest.java

The image is loaded by the ClassRequiringImage class with the code line I described 
earlier. The Main class can be executed and uses the ClassRequiringImage class. But when 
it does so, getClass().getResourceAsStream("/myImage.png") returns null (which 
is logical, I should but the image in src/main/java for this code to work).

I have a second project, MyProjectB that depends on the first one. It is not 
using Maven to compile and run but Ant. To use the classes of MyProjectA, I 
just copied the jar in MyProjectB class path.
When MyProjectB uses the ClassRequiringImage class from the MyProjectA project, as the 
image is at the root of the JAR, getClass().getResourceAsStream("/myImage.png") 
returns the image.

The problem is that I want to have both ways of using the code to work. At 
first, I had a resource package com.mycompany.app.resource containing the 
image, but Maven does not seem to include its content when packaging the JAR. 
This is why I tried to comply with the convention and moved my files to 
src/main/resources.

Benoît


Le 6 avr. 2010 à 15:16, maven apache a écrit :

   

2010/4/6 Benoît Thiébault

 

Hi everyone,

This is certainly a very dumb question but I have trouble accessing my
resources that are located in the src/resource directory.

In my code, to load an image, I do:
ImageIO.read(getClass().getResourceAsStream("/myImage.png"))

When Maven packages my software, it puts everything in the resource
directory at the root of the JAR file.
So when I use my software from another code, including the jar in the
classpath, it works.

   

What does the " my software " mean? Can you show the structure of your
project?

 

But if I use my software as a standalone application (without packaging it
in a jar file), it can't find the image (which is logical because the file
in not at the same place than in the jar).

How do you solve this problem ? Do I really have to run my app from the jar
? How can I configure Eclipse (with m2eclipse plugin installed) to run my
code correctly ?

Thank you
Benoît


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


   


Benoît Thiébault

   Artenum - Science&  Groupware
   http://www.artenum.com

   24, rue Louis-Blanc, 75010 Paris
   tel/fax : +33 (0)1 46 94 67 54


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Fully automated building from Source Control

[Markku Saarela]

Hi,

You could use Maven SCM plugin for bootstrapping the project with 
minimal pom.


http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html

rgds,

Markku

On 3.4.2010 0:09, Steve Cohen wrote:

Ok, your needs are probably more extreme than mine.  I HAPPEN at present
to be the only developer actively engaged on this project so I can get
away with non-holy-grail stuff - which explains why I stayed so long
with the Eclipse setup, but I would still like to get to the
single-command-line total rebuild from scratch.

I have less need for CI and as the only developer I can even get away
with a local repository (for now) but I would still like to move this
ball down the field so it would be easier to extend should things get
more complicated.

Are you saying then, that managing of builds at this level must depend
on something outside of Maven?  I'm not likely to find funding for
anything more sophisticated than that (I work for a budget-strapped
small team inside a large corporation that is off to the side), so I am
interested in a solution that depends on nothing beyond Maven itself.
We have and use Subversion, and that's about it.



David Hoffer wrote:
   

That "holy grail" is the only way to use maven, imho.  I don't know
about a single documentation source but there is lots of info
available on the web to achieve this.

In short we use TeamCity for CI, Artifactory for corporate maven repo,
SVN&  Maven.

-Dave


On Fri, Apr 2, 2010 at 2:48 PM, Steve Cohen  wrote:
 

Over the past few months I have slowly and, on the whole successfully,
migrated a project that was based on Eclipse to one that is based on
maven (and m2eclipse), in the process, learning much about Maven and I'm
generally quite happy with it.  It's a nice improvement.

The one step I haven't taken yet is generating a fully automated build
starting with pristine sources, checking everything it needs out from
Source Control and then building it.  That has always seemed to me to be
the "holy grail" of automated building, going back to the make days.
You "nuke" all the source, get a fresh copy from the source control
(tied to a given tag) and build from scratch.  We don't want anything
from a developer's working copy involved in any way.

I haven't done this with Maven yet and to be fair, I also hadn't done it
with the earlier Eclipse-based system in use here but I still want to do
it.  And yes, I understand that there is a bit of a chicken-egg problem
here - where is this definition of "everything" to be version controlled
and how do you avoid nuking that?  So there has to be something of a
two-tier setup.  I know this and accept it.

I hadn't spent much time looking at the Maven SCM plugin, but now that I
have, I don't really see what I'm looking for there.  The examples tend
to be very sparse, and "Maven - The Definitive Guide" doesn't even touch
the SCM plugin.

Can someone point me at documentation directed toward achieving this
"holy grail" with Maven?

Thanks.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


   

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven ear plugin -- add files into META-INF folder

[Markku Saarela]

You could use 
${project.build.outputDirectory} and 
use normal build resources




src/main/resources
true



and put this weblogic file in subdirectory META-INF also you can define 
additional resource directories there.. This way you can also filter 
these files.


rgds,

Markku

On 16.3.2010 8:16, Thunder Farmer wrote:

Thanks.

I do look into the "earSourcesDirectory" parameter.
The problem is that files specified by "earSourcesDirectory " will be under
root directory of the ear, rather than under ear/META-INF.
Any idea for my issue?

I just want some files out of default folder "src\main\application\META-INF"
to be parckaged into ear/META-INF/

Thanks,
Thunder

On Tue, Mar 16, 2010 at 1:18 PM, Markku Saarelawrote:

   

Hi,

As in
http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.htmlnoted
 use earSourcesDirectory.

Rgds,

Markku


On 16.3.2010 5:06, Thunder Farmer wrote:

 

Dear all,

During ear packaging, is there any way to add my personal files into the
ear/META-INF folder if I don't put it in the default source folder
"src\main\application\META-INF".
For example, I have weblogic specific file "weblogic-application.xml", it
dost't lie in the default folder "src\main\application\META-INF", what
could
I do in this case?
I am using maven 2.1.0-M1.

any idea would be appreciated.

Thanks,
Thunder



   
 


   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven ear plugin -- add files into META-INF folder

[Markku Saarela]

Hi,

As in 
http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.html 
noted use earSourcesDirectory.


Rgds,

Markku

On 16.3.2010 5:06, Thunder Farmer wrote:

Dear all,

During ear packaging, is there any way to add my personal files into the
ear/META-INF folder if I don't put it in the default source folder
"src\main\application\META-INF".
For example, I have weblogic specific file "weblogic-application.xml", it
dost't lie in the default folder "src\main\application\META-INF", what could
I do in this case?
I am using maven 2.1.0-M1.

any idea would be appreciated.

Thanks,
Thunder

   

Re: Release schedule for ear plugin version 2.4.1

[Markku Saarela]

Thanks for good news.

Markku

On 17.2.2010 0:29, Stephane Nicoll wrote:

The release vote for 2.4.1 has just been sent on the dev list.

S.

On Tue, Jan 19, 2010 at 8:47 AM, Markku Saarelawrote:

   

Hi,

What is plan for releasing version 2.4.1 of ear plugin? All issues for this
release are resolved.

rgds,

Markku


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


 


   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven central has corrupted artifact org.apache.xbean:xbean-finder-shaded:jar:3.6

[Markku Saarela]

Thanks for your effort. I turn to Geronimo community.

markku

On 27.1.2010 16:53, Wendy Smoak wrote:

On Wed, Jan 27, 2010 at 7:16 AM, Markku Saarela  wrote:

   

org.apache.xbean:xbean-finder-shaded:jar:3.6 artifact MD5 checksum does not
match, so our Artifactory reject it's download.

So where can i get original jar file?
 

I wouldn't assume the jar is wrong without verifying the gpg
signature... which I can't do because the public key is nowhere to be
found.

This needs to be addressed by the XBean project developers, not here.
I forwarded your note to d...@geronimo (assuming it doesn't bounce; I'm
not subscribed) to ask the developers about the problem.

   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven central has corrupted artifact org.apache.xbean:xbean-finder-shaded:jar:3.6

[Markku Saarela]

Hi,

org.apache.xbean:xbean-finder-shaded:jar:3.6 artifact MD5 checksum does 
not match, so our Artifactory reject it's download.


So where can i get original jar file?

rgds,

Markku

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Release schedule for ear plugin version 2.4.1

[Markku Saarela]

Hi,

What is plan for releasing version 2.4.1 of ear plugin? All issues for 
this release are resolved.


rgds,

Markku

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Can I skip these warnings and compile legacy classes in Maven?

[Markku Saarela]

Hi,

You can configure compiler plugin to use certain compiler version

http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html

also you can put additional target and source definitions in the same
compiler plugin configuration

http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html

rgds,

Markku



Kevin wrote:
> I'm moving a legacy project into Maven2, but there're some classes
> using the SUN deprecated API which are not recommended now, so I get a
> failure message when running mvn compile.
>
> [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\utility\CheckCode.java:[11,31]
> 警告：com.sun.image.codec.jpeg.JPEGCodec 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\utility\CheckCode.java:[12,31]
> 警告：com.sun.image.codec.jpeg.JPEGEncodeParam 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\utility\CheckCode.java:[13,31]
> 警告：com.sun.image.codec.jpeg.JPEGImageEncoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\side\Base64.java:[8,10]
> 警告：sun.misc.BASE64Encoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\side\Base64.java:[8,47]
> 警告：sun.misc.BASE64Encoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\side\Base64.java:[13,10]
> 警告：sun.misc.BASE64Decoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\side\Base64.java:[13,47]
> 警告：sun.misc.BASE64Decoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\utility\CheckCode.java:[133,2]
> 警告：com.sun.image.codec.jpeg.JPEGImageEncoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\utility\CheckCode.java:[133,29]
> 警告：com.sun.image.codec.jpeg.JPEGCodec 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\utility\CheckCode.java:[134,2]
> 警告：com.sun.image.codec.jpeg.JPEGEncodeParam 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\article\ad\Base64.java:[8,10]
> 警告：sun.misc.BASE64Encoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\article\ad\Base64.java:[8,47]
> 警告：sun.misc.BASE64Encoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\article\ad\Base64.java:[13,10]
> 警告：sun.misc.BASE64Decoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> D:\ideaprojects2\bbs\foo\src\main\java\bar\baz\article\ad\Base64.java:[13,47]
> 警告：sun.misc.BASE64Decoder 是 Sun 的专用 API，可能会在未来版本中删除
>
> and these classes wouldn't be compiled. Is there anyway that I can
> just ignore the warnings and succeed in compiling without replacing
> the codes?
>
> My JDK version:
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>
> TIA.
>   


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Assembly will not deploy.

[Markku Saarela]

Hi,

You can use build-helper:attach-artifact 
 
to gain that behavior.


http://mojo.codehaus.org/build-helper-maven-plugin/

rgds,
Markku

David C. Hicks wrote:

Hi,

I have a module in my project that creates an assembly to be deployed 
to our Nexus repository - only the assembly won't deploy.  This was 
working until this particular build.  I've been using the deprecated 
"attach" goal to cause the assembly to be added to the list of 
artifacts to be deployed.  Suddenly, the assembly will build but not 
deploy.


We're using Maven 2.0.9 with Assembly plugin 2.2-beta-2.

Any thoughts why this would suddenly stop working?  Or, maybe a 
different way to get the desired result?


Thanks,
Dave


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Source Plugin config to include generated-sources?

[Markku Saarela]

Hi,

Try build-helper plugin for adding this target/geratated-sources directory.

http://mojo.codehaus.org/build-helper-maven-plugin/add-source-mojo.html

rgds,

Markku

David Hoffer wrote:

As far as I can tell this won't work, I think this just includes excludes
files that are already in the right/included folders.

I need a way to add the files in ${basedir}/target/generated-sources to jar
of sources that it creates.

Does anyone know how to do this?

-Dave


On Thu, Aug 6, 2009 at 7:05 PM, David Hoffer  wrote:

  

Any idea what the format of path1 & path2 are?

I have tried:


${basedir}/src/main/java/**

${basedir}/target/generated-sources/**


And


${basedir}/src/main/java

${basedir}/target/generated-sources


Always says no files have been included so it errors out.

-Dave


On Thu, Aug 6, 2009 at 3:57 PM, Benson Margulies wrote:




 path1
 path2


On Thu, Aug 6, 2009 at 5:14 PM, David Hoffer wrote:
  

Here is the error.

Cause: Cannot assign configuration entry 'includes' to 'class
[Ljava.lang.String
;' from
'C:\iss_svn\CDF\trunk\cdf-webtas/src/main/java/**/*.java,C:\iss_svn\CDF\
trunk\cdf-webtas/target/generated-sources/**/*.java', which is of type


class
  

jav
a.lang.String

-Dave

On Thu, Aug 6, 2009 at 3:12 PM, David Hoffer 


wrote:
  

Perhaps I don't understand the format of this, I tried the following
  

and
  

get an error:




  

${basedir}/src/main/java/**/*.java,${basedir}/target/generated-sources/**/*.java
  



-Dave


On Thu, Aug 6, 2009 at 2:45 PM, Alexander 
  

wrote:
  

Wont help you *includes *goal?





http://maven.apache.org/plugins/maven-source-plugin/aggregate-mojo.html#includes
  

2009/8/7 David Hoffer 



How can I configure the Maven Source Plugin to include source files
  

in
  

the


/target/generated-sources folder?  I would assume it would do this
  

by
  

default but I don't even see a way to configure this.  It always
  

ignores
  

additional source here.  Can somebody help me?

-Dave

  


--
Regards,
Alexander


  

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


  


  



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: copy\move plugin

[Markku Saarela]

Also you could use jar plugin to make extra artifact for project with 
classifier like server and configure that jar plugin execution to 
include server specific resource files.


- Markku Saarela

Alexander Vaysberg wrote:
I think, it was better the common project, server and  client project 
created. But other solution can be a assembling plugin. The first 
soluction with project for me was better. I can a release for common, 
client and server make. With assembling can I only default release 
make but not for client and server, or?


Jonathan Woods schrieb:

Then it might be more naturally 'Maven' to have 3 projects, 2 of them
depending on the common third.
 

-Original Message-
From: Alexander [mailto:the.malk...@gmail.com] Sent: 23 July 2009 10:37
To: Maven Users List
Subject: Re: copy\move plugin

Nope, client looks exactly like server. They have no code 
difference. Only some configuration files.


2009/7/23 Alexander Vaysberg 

   
The simply was create 2 project client and server. You can it make 
with multi-project. In this case you have a separetly you   
client and

server application.

Alexander schrieb:

 Hello,
 
I must distribute different set of resource files\ bat 
files\ images
at server and client application. For server I have to 
copy bat files
to register in servers, properties with db configuration 
and so on.

But client don't need them - it only connects to server.

I want to type "mvn package" and after moment see two distrinct 
folders for server and client use.


2009/7/23 Alexander Vaysberg 



   
The Maven is not same as Ant. The first question is why   
you need the
same file on different places? If you try make a project   
for alls,

that the maven, isn't for you.

Alexander schrieb:

 Hello,


 
It seems like it is impossible to copy one file to several 
different locations not under target directory. Sure, I can copy 
several different files to one directory but not otherwise.


2009/7/23 Lewis, Eric 





   
No, by specifying outputDirectory, you can copy   

anywhere you like.
   

See



  

http://maven.apache.org/plugins/maven-resources-plugin/copy-resour
   

ces-mojo.html

Just make sure your files aren't filtered, for instance


 my_output
 
 
   my_input
   false
 
 


It's really flexible, read the examples, for instance 
  
'Including

and excluding files and directories'.

Best regards,
Eric





 

-Ursprüngliche Nachricht-
Von: Alexander [mailto:the.malk...@gmail.com]
Gesendet: Donnerstag, 23. Juli 2009 09:48
An: Maven Users List
Betreff: Re: copy\move plugin

Hello,

You copy files to output (target) directory or to any other? I 
thought resource plugin helps with copying files from 

somewhere

to output (target) only directory.

2009/7/23 Lewis, Eric 





   

I do my copying with the resource plugin, which works nicely.

Best regards,
Eric





 

-Ursprüngliche Nachricht-
Von: Alexander [mailto:the.malk...@gmail.com]
Gesendet: Donnerstag, 23. Juli 2009 08:32
An: Maven Users List
Betreff: Re: copy\move plugin

Hello,

I knew about that plugin, but thanks anyway. With that






plugin I could


  
   

emulate so many maven plugins, you know.. But I'm trying to


 

move to maven
from ant and wondering if I could use some maven kung-fu.

2009/7/23 Dan Tran 





   

maven-antrun-plugin?



On Wed, Jul 22, 2009 at 11:24 PM,




  

Alexander wrote:




   

Hello all,


 

Does maven have any plugin that provides simple task as






copy\move files?


  
   

Sure, I could invoke ant task but really want to do all


 


in *maven style.


  
   

*I




 

need to juggle with files a little. *
*






  


---
   

--




To unsubscribe, e-mail: users-unsubscr...@maven.apache.org


 

For additional commands, e-mail: users-h...@maven.apache.org
   





  


---
   

--




To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org






  

-
   






To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For a

Re: [PLEASE TEST] Maven 2.2.0-RC3

[Markku Saarela]

Same thing. With RC2 release failed but now with RC3 releases of 
multi-module projects success :-).


- markku

Jörg Schaible wrote:

Dominic Mitchell wrote at Mittwoch, 17. Juni 2009 10:02:

  

On 16 Jun 2009, at 20:08, Nayan Hajratwala wrote:



sorry you're having so much trouble, robert -- i just tested 2.2.0-
RC3, and
it worked fine for me. Good luck on IRC!
  

I agree — I installed 2.2.0-RC3 onto my path a couple of days ago and
promptly forgot about it.  :)   I haven't noticed any changes since,
which is a Good Thing™.



Same to me. However, with RC2 I could not release and IO have not tried with
RC3 yet.

- Jörg


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

  



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [PLEASE TEST] Maven 2.2.0-RC2

[Markku Saarela]

Hi,

Our release failed. There are two problems.

Command line: mvn -Psome -Denv=some-dev release:perform -X

1. Command line -Psome profile activation is not working, at least 
prepare perform and rollback goals.

[WARNING]
   Profile with id: 'some' has not been activated.

2. release:perform failed for some weird -f option

[INFO] Failed to re-parse additional arguments for Maven invocation.

Unrecognized option: -f
[INFO] 


[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
re-parse additional arguments for

Maven invocation.
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor

.java:703)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycl

eExecutor.java:553)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.

java:523)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultL

ifecycleExecutor.java:371)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleE

xecutor.java:268)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java

:181)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
   at 
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to 
re-parse additional arguments f

or Maven invocation.
   at 
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:133)
   at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor

.java:678)
   ... 16 more
Caused by: org.apache.maven.shared.release.ReleaseExecutionException: 
Failed to re-parse additional

arguments for Maven invocation.
   at 
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase

.java:89)
   at 
org.apache.maven.shared.release.phase.RunPerformGoalsPhase.execute(RunPerformGoalsPhase.j

ava:67)
   at 
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:

336)
   at 
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:

282)
   at 
org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:

262)
   at 
org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:129)

   ... 18 more
Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: 
Failed to re-parse additiona

l arguments for Maven invocation.
   at 
org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecut

or.java:335)
   at 
org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecut

or.java:377)
   at 
org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecut

or.java:413)
   at 
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase

.java:81)
   ... 23 more
Caused by: org.apache.commons.cli.UnrecognizedOptionException: 
Unrecognized option: -f

   at org.apache.commons.cli.Parser.processOption(Parser.java:363)
   at org.apache.commons.cli.Parser.parse(Parser.java:199)
   at org.apache.commons.cli.Parser.parse(Parser.java:85)
   at 
org.apache.maven.shared.release.exec.InvokerMavenExecutor.setupRequest(InvokerMavenExecut

or.java:186)
   ... 26 more

rgds,

Markku

John Casey wrote:

Hi again,

After finding and cleaning up some code that seems to be tainted 
during some of our efforts at generifying the codebase, we've respun a 
new release candidate.


If you have time, please give it a whirl:

https://repository.apache.org/content/repositories/maven-staging-010/org/apache/maven/apache-maven/2.2.0-RC2/ 



Remember, if you have any problems, report them to: 
http://jira.codehaus.org/browse/MNG with Affects-Version: 2.2.0


...then, please reply to this thread to let me know about 

resources plugin failed to use properties in release:prepare for multi module projects

[Markku Saarela]

Hi,

Using Maven 2.1.0, release-plugin 2.0-beta-8 and resources-plugin 2.3.

When performing normal mvn install for multi-module project all builds 
succes, but when trying release projekts, those projects that have 
filter files whitch are specified in profiles via properties failed.


Resources plugin is not configured at all by properties. Any ideas or 
workarounds.


[INFO] [DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-resources-plugin:2.3:resources' -->

[INFO] [DEBUG]   (f) encoding = UTF-8
[INFO] [DEBUG]   (f) filters = [C::\xxx\xxx\xx\\${filter.file}]

[INFO] [DEBUG]   (s) includeEmptyDirs = false
[INFO] [DEBUG]   (s) outputDirectory = C:\xxx\xxx\xx\target\c
lasses
[INFO] [DEBUG]   (s) overwrite = false
[INFO] [DEBUG]   (f) project = MavenProject: xxx.xxx.:2.0 @ C:\projects
\xxx\xxx\xxx\pom.xml
[INFO] [DEBUG]   (s) resources = [Resource {targetPath: null, filtering: 
true, FileSet {directory: C

:\xxx\xxx\src\main\resources, PatternSet [includes: {}, ex
cludes: {}]}}]
[INFO] [DEBUG]   (f) session = 
org.apache.maven.execution.mavensess...@d1ad08

[INFO] [DEBUG] -- end configuration --
[INFO] [INFO] [resources:resources]
[INFO] [INFO] 


[INFO] [ERROR] BUILD ERROR
[INFO] [INFO] 

[INFO] [INFO] Error loading property file 
'C:\xxx\xxx\xx-service\${filter.file}'


rgds,

Markku

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven extra sources and eclipse

[Markku Saarela]

Hi,

You can use build-helper plugin and its goal add-source.

http://mojo.codehaus.org/build-helper-maven-plugin/

rgds,

Markku

Jean-Marc Vanel wrote:

Hi all

 We have a projet (
http://eulergui.svn.sourceforge.net/viewvc/eulergui/trunk/eulergui/pom.xml
) using a parser generator , for which we have extra Java sources, not
for building with the application.

We generate the eclipse configuration with Maven, but I found no way
to specify these extra Java sources so that they appear in the eclipse
configuration.

Thanks for any hint
  



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Release Plugin

[Markku Saarela]

Hi,

configure release plugin  goals element  as described in 
http://maven.apache.org/plugins/maven-release-plugin/examples/perform-release.html


- markku

Terry Bell wrote:
Is there any way to stop the release:perform from generating any 
reports at all?


I would looking for an option that just does the subversion tagging 
commits, and the artifactory uploads.


-tb

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [POLL] Default Value for Reports Output Encoding

[Markku Saarela]

[b] Use source files encoding, because then only one encoding value is need to 
set for project if desired(if neither of source or reporting encoding is set 
then platform specific is used).

- markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Add Generated Src to IDE build path?

[Markku Saarela]

Hi,

Use  plugins Build Helper Maven plugins add-source goal in your pom.xml 
that resolves all of those proplems.


http://mojo.codehaus.org/build-helper-maven-plugin/

- markku

Clifton wrote:

Hello,

I'm having lots of trouble with a Maven project that generates source. In my
project a crude wiring framework is created from a template and a properties
file creating an Assembler.java class that plugs implementations into
collaborators. This class needs to be on our IDE build path
(Eclipse/IntelliJ) in order for other classes to resolve. Using the Maven
support in these IDEs the build path is naturally managed by Maven, which
takes the resrouces and src folders declared in the POM and puts them on the
build path along with dependency jars. I can manually set an extra build
path entry but that fights the Maven support which undoes my manual entry
when it synchronizes. Maven only seems to allow a single source folder
entry. I had to set low level compiler flags to get the generated folders
included in the compile process. I used
target/gensrc
as this was the only way I could find to get Maven to build the project. I
also tried sneaking the generated source folder into the resources path to
get it into IDE visibility but since it's under the target folder it is
overridden by the "exclude output folders" setting that Maven support
enables. So my question is how do you properly manage generated source in a
Maven project? Any/all advice is welcome.
  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 2nd compile phase?

[Markku Saarela]

In that case you could try configure compile plugin for two executions 
one bind for normal compile phase and another bind to prepare-package 
phase that also compiles these third-party generated classes.


- markku

De Smet Ringo wrote:
Markku, 

  

-Original Message-
From: Markku Saarela [mailto:[EMAIL PROTECTED] 
Sent: maandag 7 juli 2008 11:11

To: Maven Users List
Subject: Re: 2nd compile phase?

Hi,

You could split project to three different ones. One for this 
actual ejb project that then depends on you third-party 
project and which depends you original source code project.



Thanks for the tip, but this is not an option for now. I may not disrupt
the current Maven 1 based project setup. Once we are completely on Maven
2, we can do project refactorings to simplify things, but not at this
moment.

Ringo
*

Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. 


This e-mail and any attachment thereto may contain information which is 
confidential and/or protected by intellectual property rights and are intended 
for the sole use of the addressees. Any use of the information contained herein 
(including but not limited to total or partial reproduction or distribution in 
any form) by other persons than the addressees is prohibited. If you have 
received this e-mail in error, please notify the sender and delete its contents.

Ce courriel et les annexes éventuelles peuvent contenir des informations 
confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce 
message est adressé exclusivement à son (ses) destinataire(s). Toute 
utilisation du contenu de ce message (y compris la reproduction ou diffusion 
partielle ou complète sous toute forme) par une autre personne que le(s) 
destinataire(s) est formellement interdite. Si vous avez reçu ce message par 
erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu.

*

-
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]

Re: 2nd compile phase?

[Markku Saarela]

Hi,

You could split project to three different ones. One for this actual ejb 
project that then depends on you third-party project and which depends 
you original source code project.


regards,

markku'

De Smet Ringo wrote:

Hello,
 
I am in the need of triggering a second compile phase. During our build,

we have a third-party tool, integrated using the antrun plugin in the
process-classes phase, that uses a descriptor file and a classpath
(contains our already compiled manually written java classes) and
generates additional sources. These need to be compiled before the
ejb:ejb goal can run successfully. I searched through the archives, but
couldn't find a similar problem description.
 
Ringo De Smet

ixor
 
*


Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. 


This e-mail and any attachment thereto may contain information which is 
confidential and/or protected by intellectual property rights and are intended 
for the sole use of the addressees. Any use of the information contained herein 
(including but not limited to total or partial reproduction or distribution in 
any form) by other persons than the addressees is prohibited. If you have 
received this e-mail in error, please notify the sender and delete its contents.

Ce courriel et les annexes éventuelles peuvent contenir des informations 
confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce 
message est adressé exclusivement à son (ses) destinataire(s). Toute 
utilisation du contenu de ce message (y compris la reproduction ou diffusion 
partielle ou complète sous toute forme) par une autre personne que le(s) 
destinataire(s) est formellement interdite. Si vous avez reçu ce message par 
erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu.

*

-
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]

Re: [SURVEY] How does your team retrieve artifacts?

[Markku Saarela]

[X] Our team uses HTTP to retrieve our artifacts

regards,

- markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: jars appear timestamped in wars and zips since 2.0.9

[Markku Saarela]

They are wrong because dependency is for -SNAPSHOT versions and 
manifests in jars has classpath to these -SNAPSHOT versions and 
therefore classes from these wrongly named jar in war lib directory 
can't be found. War plugin should get these new timestamped jars from 
local repo and rename them correctly to -SNAPSHOT as ear plugin does


- markku
.
Brian E. Fox wrote:

Are you saying the artifacts are _wrong_ or you just don't like the timestamp'd 
file name? Usually the timestamp'd name indicates the file came from a remote 
repo, which could happen depending on various settings and if it's newer on the 
remote.

-Original Message-
From: Markku Saarela [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 25, 2008 6:04 AM

To: Maven Users List
Subject: Re: jars appear timestamped in wars and zips since 2.0.9

Hi,

While debugging 2.1-alpha-1 war plugin in method

ArtifactsPackagingTask.performPackaging( WarPackagingContext context )

DefaultArtifact class instance has right version number and also method 
getArtifactFinalName( context, artifact ); returns right name -SNAPSHOT 
also.


But when removing all breakpoints and resuming execution all the rest 
snapshot artifacts has wrong filename in lib directory


- markku

Markku Saarela wrote:
  

Hi,

This start to happen at least we use Maven 2.0.8 version and still 
exists in 2.0.9.  Tested with war plugin versions 2.0.2 and 2.1-alpha-1

Here is snipped from
[DEBUG] Adding managed dependencies for 
[DEBUG]net.sourceforge.jivalo.fw:jivalo-fw-common:jar:1.5-beta-3-SNAPSHOT
[DEBUG] jivalo-fw-client: resolved to version 
1.5-beta-3-20080415.204821-1 from repository jivalo-snapshot


Classpath is correct for compiling (uses -SNAPSHOT version and not 
timestamped one)  and manifest files in jars.


Maven decides to use remote repositories constantly  allmost  every 
SNAPSHOT versions,  not for all.


Reason seems to be lastUpdated timestamp in artifacts local repository 
-SNAPSHOT directory maven-metadata-local.xml file. It is not updated 
to newer than remote repository's timestamp at that time than new 
version is retrieved from remote repository..


Best workaround i found is:
set snapshot versions to provided scope and use dependency plugins 
copy-dependencies goal.


- markku

[EMAIL PROTECTED] wrote:


Hi,
In Maven 2.0.8 I  built my war with maven-war-plugin:2.1-alpha-1 and 
my zip with maven-assembly-plugin:2.2-beta-2


The war/zip contained dependent jars as 
"jarname-version-SNAPSHOT.jar" when the depend jars were located in 
the localrepository.
The war/zip contained dependent jars as 
"jarname-version-timestamp.jar" when the depend jars were located in 
the central (company) repository and first need to be downloaded.


The difference was in the mavenmetadata-local.xml, where a 
"true entry exists:


   
...
 
 
  true   
...
  
  

Now, In Maven 2.0.9 I still built my war with 
maven-war-plugin:2.1-alpha-1 and my zip with 
maven-assembly-plugin:2.2-beta-2


But now, the mavenmetadata-local.xml file doesn´t contain a 
"true entry anymore - even if I paste one, it 
gets deleted during the build !
This results in always getting wars/zips containing dependent jars as 
"jarname-version-timestamp.jar".


And that´s not very nice, because in the MANIFEST.MF of same jars the 
""jarname-version-SNAPSHOT.jar" is mentioned, which doesn´t match the 
content of the war/zip,
Resulting in "NoClassDefFoundError" and so on, caused by an invalid 
classpath


The funny point about that story is that with the maven-ear-plugin  
the jars appear as ""jarname-version-SNAPSHOT.jar" in the generated 
*.ear.


=> Any idea how to fix that for the war and zip? Why is there a 
difference in handling jars between the war, ear and assembly 
plugins? Isn´t it always the same?
 



Thanx, Torsten

  
  

-
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]

Re: jars appear timestamped in wars and zips since 2.0.9

[Markku Saarela]

Hi,

While debugging 2.1-alpha-1 war plugin in method

ArtifactsPackagingTask.performPackaging( WarPackagingContext context )

DefaultArtifact class instance has right version number and also method 
getArtifactFinalName( context, artifact ); returns right name -SNAPSHOT 
also.


But when removing all breakpoints and resuming execution all the rest 
snapshot artifacts has wrong filename in lib directory


- markku

Markku Saarela wrote:

Hi,

This start to happen at least we use Maven 2.0.8 version and still 
exists in 2.0.9.  Tested with war plugin versions 2.0.2 and 2.1-alpha-1

Here is snipped from
[DEBUG] Adding managed dependencies for 
[DEBUG]net.sourceforge.jivalo.fw:jivalo-fw-common:jar:1.5-beta-3-SNAPSHOT
[DEBUG] jivalo-fw-client: resolved to version 
1.5-beta-3-20080415.204821-1 from repository jivalo-snapshot


Classpath is correct for compiling (uses -SNAPSHOT version and not 
timestamped one)  and manifest files in jars.


Maven decides to use remote repositories constantly  allmost  every 
SNAPSHOT versions,  not for all.


Reason seems to be lastUpdated timestamp in artifacts local repository 
-SNAPSHOT directory maven-metadata-local.xml file. It is not updated 
to newer than remote repository's timestamp at that time than new 
version is retrieved from remote repository..


Best workaround i found is:
set snapshot versions to provided scope and use dependency plugins 
copy-dependencies goal.


- markku

[EMAIL PROTECTED] wrote:

Hi,
In Maven 2.0.8 I  built my war with maven-war-plugin:2.1-alpha-1 and 
my zip with maven-assembly-plugin:2.2-beta-2


The war/zip contained dependent jars as 
"jarname-version-SNAPSHOT.jar" when the depend jars were located in 
the localrepository.
The war/zip contained dependent jars as 
"jarname-version-timestamp.jar" when the depend jars were located in 
the central (company) repository and first need to be downloaded.


The difference was in the mavenmetadata-local.xml, where a 
"true entry exists:


   
...
 
 
  true   
...
  
  

Now, In Maven 2.0.9 I still built my war with 
maven-war-plugin:2.1-alpha-1 and my zip with 
maven-assembly-plugin:2.2-beta-2


But now, the mavenmetadata-local.xml file doesn´t contain a 
"true entry anymore - even if I paste one, it 
gets deleted during the build !
This results in always getting wars/zips containing dependent jars as 
"jarname-version-timestamp.jar".


And that´s not very nice, because in the MANIFEST.MF of same jars the 
""jarname-version-SNAPSHOT.jar" is mentioned, which doesn´t match the 
content of the war/zip,
Resulting in "NoClassDefFoundError" and so on, caused by an invalid 
classpath


The funny point about that story is that with the maven-ear-plugin  
the jars appear as ""jarname-version-SNAPSHOT.jar" in the generated 
*.ear.


=> Any idea how to fix that for the war and zip? Why is there a 
difference in handling jars between the war, ear and assembly 
plugins? Isn´t it always the same?
 



Thanx, Torsten

  



-
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]

Re: jars appear timestamped in wars and zips since 2.0.9

[Markku Saarela]

Hi,

This start to happen at least we use Maven 2.0.8 version and still 
exists in 2.0.9.  Tested with war plugin versions 2.0.2 and 2.1-alpha-1

Here is snipped from
[DEBUG] Adding managed dependencies for 
[DEBUG]net.sourceforge.jivalo.fw:jivalo-fw-common:jar:1.5-beta-3-SNAPSHOT
[DEBUG] jivalo-fw-client: resolved to version 
1.5-beta-3-20080415.204821-1 from repository jivalo-snapshot


Classpath is correct for compiling (uses -SNAPSHOT version and not 
timestamped one)


Maven decides to use remote repositories constantly  allmost  every 
SNAPSHOT versions,  not for all.


Reason seems to be lastUpdated timestamp in artifacts local repository 
-SNAPSHOT directory maven-metadata-local.xml file. It is not updated to 
newer than remote repository's timestamp.


Best workaround i found is:
set snapshot versions to provided scope and use dependency plugins 
copy-dependencies goal.


- markku

[EMAIL PROTECTED] wrote:
Hi, 

In Maven 2.0.8 I  built my war with maven-war-plugin:2.1-alpha-1 and my 
zip with maven-assembly-plugin:2.2-beta-2


The war/zip contained dependent jars as "jarname-version-SNAPSHOT.jar" 
when the depend jars were located in the localrepository.
The war/zip contained dependent jars as "jarname-version-timestamp.jar" 
when the depend jars were located in the central (company) repository and 
first need to be downloaded.


The difference was in the mavenmetadata-local.xml, where a 
"true entry exists:


  
 

...
 
 
  true 
  

...
  
  

Now, In Maven 2.0.9 I still built my war with maven-war-plugin:2.1-alpha-1 
and my zip with maven-assembly-plugin:2.2-beta-2


But now, the mavenmetadata-local.xml file doesn´t contain a 
"true entry anymore - even if I paste one, it gets 
deleted during the build !
This results in always getting wars/zips containing dependent jars as 
"jarname-version-timestamp.jar".


And that´s not very nice, because in the MANIFEST.MF of same jars the 
""jarname-version-SNAPSHOT.jar" is mentioned, which doesn´t match the 
content of the war/zip,
Resulting in "NoClassDefFoundError" and so on, caused by an invalid 
classpath


The funny point about that story is that with the maven-ear-plugin  the 
jars appear as ""jarname-version-SNAPSHOT.jar" in the generated *.ear.


=> Any idea how to fix that for the war and zip? Why is there a difference 
in handling jars between the war, ear and assembly plugins? Isn´t it 
always the same?
 



Thanx, Torsten

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: jars appear timestamped in wars and zips since 2.0.9

[Markku Saarela]

Hi,

This start to happen at least we use Maven 2.0.8 version and still 
exists in 2.0.9.  Tested with war plugin versions 2.0.2 and 2.1-alpha-1

Here is snipped from
[DEBUG] Adding managed dependencies for 
[DEBUG]net.sourceforge.jivalo.fw:jivalo-fw-common:jar:1.5-beta-3-SNAPSHOT
[DEBUG] jivalo-fw-client: resolved to version 
1.5-beta-3-20080415.204821-1 from repository jivalo-snapshot


Classpath is correct for compiling (uses -SNAPSHOT version and not 
timestamped one)  and manifest files in jars.


Maven decides to use remote repositories constantly  allmost  every 
SNAPSHOT versions,  not for all.


Reason seems to be lastUpdated timestamp in artifacts local repository 
-SNAPSHOT directory maven-metadata-local.xml file. It is not updated to 
newer than remote repository's timestamp at that time than new version 
is retrieved from remote repository..


Best workaround i found is:
set snapshot versions to provided scope and use dependency plugins 
copy-dependencies goal.


- markku

[EMAIL PROTECTED] wrote:
Hi, 

In Maven 2.0.8 I  built my war with maven-war-plugin:2.1-alpha-1 and my 
zip with maven-assembly-plugin:2.2-beta-2


The war/zip contained dependent jars as "jarname-version-SNAPSHOT.jar" 
when the depend jars were located in the localrepository.
The war/zip contained dependent jars as "jarname-version-timestamp.jar" 
when the depend jars were located in the central (company) repository and 
first need to be downloaded.


The difference was in the mavenmetadata-local.xml, where a 
"true entry exists:


  
 

...
 
 
  true 
  

...
  
  

Now, In Maven 2.0.9 I still built my war with maven-war-plugin:2.1-alpha-1 
and my zip with maven-assembly-plugin:2.2-beta-2


But now, the mavenmetadata-local.xml file doesn´t contain a 
"true entry anymore - even if I paste one, it gets 
deleted during the build !
This results in always getting wars/zips containing dependent jars as 
"jarname-version-timestamp.jar".


And that´s not very nice, because in the MANIFEST.MF of same jars the 
""jarname-version-SNAPSHOT.jar" is mentioned, which doesn´t match the 
content of the war/zip,
Resulting in "NoClassDefFoundError" and so on, caused by an invalid 
classpath


The funny point about that story is that with the maven-ear-plugin  the 
jars appear as ""jarname-version-SNAPSHOT.jar" in the generated *.ear.


=> Any idea how to fix that for the war and zip? Why is there a difference 
in handling jars between the war, ear and assembly plugins? Isn´t it 
always the same?
 



Thanx, Torsten

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: manifest problem Please help

[Markku Saarela]

If this is EJB jar  to build, then you should configure ejb-plugin

 
   org.apache.maven.plugins
   maven-ejb-plugin
   
 

${basedir}/ejbModule/META-INF/MANIFEST.MF



- markku

I am Who i am wrote:

Hi All

I'm using maven -2.0.7 and have jar configuration has follows


org.apache.maven.plugins
maven-jar-plugin
2.2



${basedir}/ejbModule/META-INF/MANIFEST.MF





and my MANIFEST.MF @   ejbModule/META-INF/MANIFEST.MF has some custom entry,
but this file never makes into jar file, i've only the regular maven created
MANIFEST.MF only.
i also tried to with ,  nothing worked for
me.

I'm sure i'm doing something wrong, can anyone please give some working
sample for these option

Your help is very much appreciated

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: deploying without deploying - how do I turn off deployment of pom (or anyother default maven goal in a phase)?

[Markku Saarela]

Use mvn site-deploy

for more details look at http://maven.apache.org/guides/mini/guide-site.html

- markku

[EMAIL PROTECTED] wrote:

Hi,

We have some documentation which is sufficiently code-like (html built 
with xslt), that it needs to be built and deployed to a web server via a 
maven module.


I have got it working via FTP using the antrun plugin.  No problems 
there


The build of the documentation happens in the install phase (this is the 
most logical, and most developers will type "mvn install" without even 
using their brain).


I have bound the deployment of the documentation to the deploy phase (and 
used the pom packaging for my module).  This works, but it gives me a 
problem 
... when I call deploy, it also deploys the pom to the remote repository - 
which doesn't make any sense.  This is done by developers, and they 
shouldn't in general touch the remote repository.  But this _is_ a 
deployment, so I feel it is the correct phase to use.


How can I stop maven from deploying the pom.  Can't I disable the goal 
somehow?  Do I really need to create a custom lifecycle? (this seems like 
too much of a hack)


thanks in advance,

Michael

[EMAIL PROTECTED]

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] multiple sourceDirectory possible ?

[Markku Saarela]

Use maven-build-helper plugin  
http://mojo.codehaus.org/build-helper-maven-plugin/


- markku

Gex Dev wrote:

Hi,

A little problem :

Constraints :
  - have some java projects build with ant, those projects have multiple
source directories.
  - would like to build those projects with Maven2
  - the former ant build must work
  - the structure of sources mustn't be changed

How can i do this ? Maven don't allowed multiple sourceDirectory...

Regards,

Gerald Reinhart

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Generate Version class

[Markku Saarela]

Java JDK has simple way to do this. If You know some class located in 
your jar file simple way to get implementation version from this jar's 
manifest file is to call this known 
<>.getPackage().*getImplementationVersion*().


rgds,

Markku

Francois Fernandes wrote:
Yes, you're right. But the problem is that our jar is not the only one 
on the classpath. That means that it is hard to ensure that we're 
loading the right manifest file to read the version. (btw. we're 
placing version information already inside this jar.)
Loading resources even inside files causes us some trouble as we've 
got to support applets in very restrictive environments and different 
VMs (including Microsoft). That means that using a class is the most 
simple and stable way to gain version information of our product.


Francois


Kalle Korhonen schrieb:
Or, just generate and use a manifest file in META-INF. The manifest 
is meant
to be used exactly for that purpose (to hold the version etc. 
information).


Kalle


On 7/22/07, Dirk Olmes <[EMAIL PROTECTED]> wrote:


Francois Fernandes wrote:
> Hi list,
>
> for some time now I've been looking for a easy way to generate a 
simple
> class containing version information of our artifact. I know that 
it is
> possible to filter resources. But to avoid any resource loading 
issues I

> would like maven to generate such a class.
> Does anyone have a idea how to solve this? I'm sure that using 
resource
> filtering of a specific class template and then attaching the 
generated

> source(-folder) using the build-helper-maven-plugin, but is this a
> elegant way?

Maven packages a pom.porperties inside a jar's META-INF directory. I'd
use that instead of generating a class.

-dirk

--
A: Maybe because some people are too annoyed by top-posting.
Q: Why do I not get an answer to my question(s)?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


-
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]

Re: Preflight check for 2.0.7

[Markku Saarela]

mvn.bat has bug for classworld classpath:

@REM -- Regular WinNT shell
for %%i in ("%M2_HOME%"\core\boot\classworlds-*) do set 
CLASSWORLDS_JAR="%%i"


there are no core subdirectory only boot as it is in 2.0.6

- markku

Jason van Zyl wrote:

I have uploaded another version here:

http://people.apache.org/~jvanzyl/

Fixed a couple more issues.

On 4 Jun 07, at 7:08 PM 4 Jun 07, Jason van Zyl wrote:


I have built a snapshot for 2.0.7 and put it here:

http://people.apache.org/~jvanzyl/

I figure folks are going to try and squeeze in more issues so what I 
plan is let people state their case for issues and I'll slot those 
into 2.0.8. I'll look those over and push whatever I can into 2.0.7 
but I would like to call for vote on Wednesday let people mess around 
and release it on Monday.


And you can see the roadmap here:

http://jira.codehaus.org/browse/MNG?report=com.atlassian.jira.plugin.system.project:roadmap-panel 



Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
--




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Thanks,

Jason

--
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot 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]

Re: Ant's Java task in Maven?

[Markku Saarela]

Use as many execution element within executions as you need(use 
different id's):


   
 
   HelloWorld-exec-1
 
 
   HelloWorld-exec-2
 
   

- markku

hezjing wrote:

Thank you, Jo and Markku!
It is working now...

What about if I have mulitple main Java classes? With Ant, I used to
have different tasks to execute different Java classes:

  
 
  

  
 
  



On 6/4/07, Markku Saarela <[EMAIL PROTECTED]> wrote:

Use Maven Exec Plugin http://mojo.codehaus.org/exec-maven-plugin/

- markku

hezjing wrote:
> Hi Jo
>
> I hope I can do this the "Maven's way" without using the Antrun 
plugin.

>
> Any better idea?
>
>
> On 6/4/07, Jo Vandermeeren <[EMAIL PROTECTED]> wrote:
>> You can call your Ant task with the maven-antrun-plugin:
>> http://maven.apache.org/plugins/maven-antrun-plugin/
>>
>> On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote:
>> >
>> > Hi!
>> >
>> > With Ant, we have Java task to execute a main Java class.
>> >
>> > How can I do this with Maven?
>> >
>> >
>> > --
>> >
>> > Hez
>> >
>> > 
-

>> > 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]

Re: Ant's Java task in Maven?

[Markku Saarela]

Use Maven Exec Plugin http://mojo.codehaus.org/exec-maven-plugin/

- markku

hezjing wrote:

Hi Jo

I hope I can do this the "Maven's way" without using the Antrun plugin.

Any better idea?


On 6/4/07, Jo Vandermeeren <[EMAIL PROTECTED]> wrote:

You can call your Ant task with the maven-antrun-plugin:
http://maven.apache.org/plugins/maven-antrun-plugin/

On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> With Ant, we have Java task to execute a main Java class.
>
> How can I do this with Maven?
>
>
> --
>
> Hez
>
> -
> 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]

Executing same plugin more than once with different configuration at once.

[Markku Saarela]

Hi,

Due to bug http://jira.codehaus.org/browse/MNG-2708 it is impossible to 
configure exec-maven-plugin in execution element and it seams to me that 
if you specify plugin twice in build it is not executed twice. So any 
suggestions for workaround or should I make my own version of that 
plugin with default values.


rgds,
- markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to prevent eclipse plugin rad goal for web project to create src/main/webapp directory and copying dependent jars into its lib directory.

[Markku Saarela]

Hi,

Is it possible to prevent eclipse:rad goal to create src/main/webapp 
directory with all subdirectories and not to copy dependent libraries? 
This is because we are deploying Maven build ear's to Rad's WAS by WAS 
console.


rgds,

Markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Can Maven 2.X run offline?

[Markku Saarela]

Sorry for delay we have diffuculties with our corporate network.

If you intend is to mirror of central then you must mirror also plugins
like this:



central
Internal Mirror of Central Plugins Repository
file:/e:/repository1



- markku

JesseLiu wrote:
> The case is that I want to build a file repository in LAN which can't connect 
> to Internet.
> so,In pom.xml it seems like below:
> 
>   4.0.0
>   com.mycompany.dolly
>   sample
>   1.0.1
>   
>   
> 
>   central
>   Maven Repository Switchboard
>   default
>file://e:\repository1 
> 
>
> 
>
> The localRepository is default to ~/.m2/ which has no artifacts from the 
> beginning. but I am sure that the specified central repository 
> file://e:\repository1 has all the required artifacts, because it is copied 
> from another runnable maven localRepository.
>
> The mvn result is :
> E:\mvndemo\my-app>mvn -o compile
> [INFO]
> NOTE: Maven is executing in offline mode. Any artifacts not already in your 
> local
> repository will be inaccessible.
>
> [INFO] Scanning for projects...
> [INFO] 
> -
> ---
> [INFO] Building Unnamed - com.mycompany.dolly:sample:jar:1.0.1
> [INFO]task-segment: [compile]
> [INFO] 
> -
> ---
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not 
> exist or no valid version could be found
> [INFO] 
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO] 
> 
> [INFO] Total time: < 1 second
> [INFO] Finished at: Wed Mar 14 18:35:39 CST 2007
> [INFO] Final Memory: 1M/2M
> [INFO] 
> 
>
>
> Thanks for any suggestion?
>
>
>
>
> - Original Message - 
> From: "Markku Saarela" <[EMAIL PROTECTED]>
> To: "Maven Users List" 
> Sent: Wednesday, March 14, 2007 6:09 PM
> Subject: Re: Can Maven 2.X run offline?
>
>
>   
>> Yes. Use -o command line argument.
>>
>> - markku
>>
>> JesseLiu wrote:
>> 
>>> With Regards,
>>> Jesse Liu
>>> ~~
>>> Tel: 86-755-2699 5598
>>> Email: [EMAIL PROTECTED]
>>> Skype: liujiasong
>>> MSN: [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]

Re: File system reference to parent POM

[Markku Saarela]

Use ../pom/pom.xml in your parent 
element of POM if this parent POM is somewhere in you checked out source 
tree.


- markku

Kristian Nordal wrote:

On 3/14/07, olivier jacob <[EMAIL PROTECTED]> wrote:


On 3/14/07, Kristian Nordal <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I've noticed that Maven2 uses a file system reference to the parent 
POM

-
> if
> the parent POM is located in the directory above. This is causing
problems
> when someone in the team is working on a specific module, but at some
> point
> did a check out of the complete source tree / module hierarchy. New
> snapshots of the parent pom are deployed by Continuum. Is it 
possible to
> force maven to always use the snapshots found in the repository 
(running

> with -U didn't help) / disabling file system reference to parent?


I think you can deploy your parent POM in your repository. This way, you
won't have to specify the file system reference.



Yes, and Continuum deploys snapshots of the parent. If you only do a 
check

out of the single module, it works fine. The problem is when you actually
have the complete source tree / module hierarchy, but is only working 
on one
specific module. If the parent pom is in the directory above, it uses 
that

POM (which isn't necessarily up-to-date) instead of the one in the
repository. This isn't a major issue, but the developers generally 
want to
have the complete source tree - even if they're only working on parts 
of it.


--
Cheers,
Kristian




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Can Maven 2.X run offline?

[Markku Saarela]

Yes. Use -o command line argument.

- markku

JesseLiu wrote:
> With Regards,
> Jesse Liu
> ~~
> Tel: 86-755-2699 5598
> Email: [EMAIL PROTECTED]
> Skype: liujiasong
> MSN: [EMAIL PROTECTED]
> ~~


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Renaming file with Maven 2 without Ant

[Markku Saarela]

Yes I know, I have allready done this plugin, but I just wanted to know 
if some plugin has allready this functionality ;-).


Markku

Wayne Fay wrote:

Mojo plugins (for something like this) are exceptionally trivial --
you should give it a try.

Wayne

On 3/7/07, Markku Saarela <[EMAIL PROTECTED]> wrote:

And even without writing own mojo, witch i do if it the only solution.

- markku

Markku Saarela wrote:
> Hi,
>
> Is it possible to rename file with Maven2 without Ant? I spent some
> time for digging this information for web but no luck.
>
> rgds,
>
> Markku
>
> 
> 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]

Re: Renaming file with Maven 2 without Ant

[Markku Saarela]

And even without writing own mojo, witch i do if it the only solution.

- markku

Markku Saarela wrote:

Hi,

Is it possible to rename file with Maven2 without Ant? I spent some 
time for digging this information for web but no luck.


rgds,

Markku


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]

Renaming file with Maven 2 without Ant

[Markku Saarela]

Hi,

Is it possible to rename file with Maven2 without Ant? I spent some time 
for digging this information for web but no luck.


rgds,

Markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: javax.jms in not repo

[Markku Saarela]

Hi,

Look at documentation 
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html


- markku

Wim Deblauwe wrote:

Hi,

seems that the javax.jms is not correctly in the repository. Using
mvnrepository I found that it should be in the javax.jms group, but 
looking
into the repo (http://repo1.maven.org/maven2/javax/jms/jms/1.1/) I see 
only

the pom, not the jar file.

Who should I bother with this?

regards,

Wim




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Renaming archetype files at custom archetype create goal?

[Markku Saarela]

Hi,

Is it possible somehow to rename files witch locates under 
archetype-resources in you custom archetype?


What i want to do is rename baseMagicDraw11.5model.xml file to 
${artifactId}.xml file when performing create goal.


Thanks,

Markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven-compiler-plugin missing in central (ibiblio)?

[Markku Saarela]

Hi,

look at:  
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/plugins/maven-compiler-plugin/ 
instead.


- markku

hochraldo wrote:

Hi!

I am getting an error that the maven-compiler plugin can not be found in
central. 
If i take a look at

http://mirrors.ibiblio.org/pub/mirrors/maven2/maven/maven-compiler-plugin/
the directory is empty.
Has the maven-compiler-plugin been deleted?

Btw. i am using maven version 2.0.5.
  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven-ear-plugin 2.3 version unwanted behavior with ejb-client dependencies

[Markku Saarela]

Hi,

That is useful trick.

Thanks,
Markku

Janecek Jan wrote:

Hi,

Let ejb plugin generate client ejb jar. Then use dependency on this
client jar (with type jar and classifier client) instead of the
dependency on the server ejb jar (which has type ejb). This works fine.

Regards,
Jan

-Original Message-
From: Markku Saarela [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 1:51 PM

To: Maven Users List
Subject: maven-ear-plugin 2.3 version unwanted behavior with ejb-client
dependencies

Hi,

With new maven-ear-plugin 2.3 version i get unwanted java modules is
application.xml.

We have module structure where ejb module has another ejb module as
ejb-client dependent. Now with this 2.3 version this dependents
ejb-client dependent shows up is application.xml. If i exclude this
ejbclientmodule in configuration then the ejb-client jar file does not
showup is ear file.

Any ideas?

rgds,

Markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



 
 
Tento e-mail je urcen pouze pro jeho adresata/adresaty a muze obsahovat duverne informace, jejichz ochrana muze byt vyzadovana pravnimi predpisy.

Jestlize jste zpravu obdrzel(a) omylem, neprodlene informujte jejiho 
odesilatele a tuto zpravu, jeji prilohy a pripadne kopie ihned vymazte. 
Jakakoli forma uziti, zverejneni, reprodukce, kopirovani, distribuce a sireni 
teto zpravy je v takovem pripade zakazana.
Komercni banka, a.s., neodpovida za mozne skody zpusobene neuplnym prenosem, 
moznou modifikaci ci zpozdenim teto zpravy behem prenosu od odesilatele k 
adresatovi.


This e-mail transmission is intended solely for the ordinary user of the e-mail address to which it was addressed. It may contain legally privileged and/or confidential information. 
If you have received this e-mail in error or are not an intended recipient please inform the sender with-out delay and delete this e-mail, attachments and possible copies immediately. The unauthorised use, disclosure, distribution and/or copying of this e-mail or any information it contains is prohibited. 
Komercni banka, a. s., does not accept liability for any damage caused by incomplete transmission, possible modification or delay of this e-mail during the transmission from the sender to the recipient.




-
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]

maven-ear-plugin 2.3 version unwanted behavior with ejb-client dependencies

[Markku Saarela]

Hi,

With new maven-ear-plugin 2.3 version i get unwanted java modules is 
application.xml.


We have module structure where ejb module has another ejb module as 
ejb-client dependent. Now with this 2.3 version this dependents 
ejb-client dependent shows up is application.xml. If i exclude this 
ejbclientmodule in configuration then the ejb-client jar file does not 
showup is ear file.


Any ideas?

rgds,

Markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: executable jar

[Markku Saarela]

Include true element to manifest 
configuration if not allready done.


Package deliverable zip file  witch have all these classpath dependency 
jars with assembly plugin.


- markku

Jane wrote:

Hi, markku,
   Thanks for your reply.

  Maybe the reason is like 1 just you said.
  The project I aims to package has a dependeny for jmf.jar. But it 
hasn't

included in the jar. How can I include it?

Jane


2007/2/8, Markku Saarela <[EMAIL PROTECTED]>:


Hi,

There are at least two way to get this exception.

1. at other machines you dont have JMF api available for executable jar.
2. Somehow at other machine you MediaLocator constructor get wrong
parameter.

- markku

Lan wrote:
> Hi,Franz,
>
>Thanks for your quick reply.
>
>The error shows:
> Exception in thread "main" java.lang.NoClassDefFoundError:
> javax/media/NoPlayerException
>
> Actually, I have difined the MainClass in POM. But in my own 
machine, it

> runs correctly.
>
> Jane
>
> 2007/2/7, franz see <[EMAIL PROTECTED]>:
>>
>>
>> Good day to you, Jane,
>>
>> What do you mean by it can only be used in your machine? What 
error are

>> you
>> getting when used in another machine?
>>
>> Cheers,
>> Franz
>>
>>
>> Lan-6 wrote:
>> >
>> > Hi, all
>> >
>> > I have generated an executable jar by using maven, (mvn 
package).

>> The
>> > jar includes the generated classes and main class.
>> > But it can only be used in my own machine. Shall I do some more
>> > settings
>> > to the project? What can I do?
>> >
>> > Thanks advance!
>> >
>> > Jane
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/executable-jar-tf3186039s177.html#a8845369
>> 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]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: executable jar

[Markku Saarela]

Hi,

There are at least two way to get this exception.

1. at other machines you dont have JMF api available for executable jar.
2. Somehow at other machine you MediaLocator constructor get wrong 
parameter.


- markku

Lan wrote:

Hi,Franz,

   Thanks for your quick reply.

   The error shows:
Exception in thread "main" java.lang.NoClassDefFoundError:
javax/media/NoPlayerException

Actually, I have difined the MainClass in POM. But in my own machine, it
runs correctly.

Jane

2007/2/7, franz see <[EMAIL PROTECTED]>:



Good day to you, Jane,

What do you mean by it can only be used in your machine? What error are
you
getting when used in another machine?

Cheers,
Franz


Lan-6 wrote:
>
> Hi, all
>
> I have generated an executable jar by using maven, (mvn package).
The
> jar includes the generated classes and main class.
> But it can only be used in my own machine. Shall I do some more
> settings
> to the project? What can I do?
>
> Thanks advance!
>
> Jane
>
>

--
View this message in context:
http://www.nabble.com/executable-jar-tf3186039s177.html#a8845369
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]

Re: Can't deploy site,Help please.

[Markku Saarela]

Hi,

You configure authentication in settings.xml.

Look here for details:  http://maven.apache.org/settings.html#Servers

rgds,

markku

jiangshachina wrote:

Hello,
I tried to deploy project via scp just now, but authentication failed.
How to set the user/password of remote machine in POM file?

a cup of Java, cheers!
Sha Jiang


Markku Saarela wrote:
  

One slash character was dropped out :-)
file:///192.1.1.0/temp/directory

- markku


Markku Saarela wrote:


Hi,

No, File protocol can deploy any directory in network where user has
access. The first slash character is defining that path is absolute two
others are some server delimiters.

file:/c:/temp vs. file:///someserver/depl or even
file://192.1.1.0/temp/directory

rgds,
markku

jiangshachina wrote:
  
  

Hello,
  



I have solved the issue by used file:///path/to/deployment/dir

  
  

"file" protocol just deploys to a local path, doesn't it?

a cup of Java, cheers!
Sha Jiang


秋秋 wrote:
  



Hi,
yes,I have solved the issue by used
file:///path/to/deployment/dir*, *
thanks.


2007/2/6, Tim Kettler <[EMAIL PROTECTED]>:

  
  

Hi,

the URL you give in the distribution management section is the HTTP
URL
of your projects site. To deploy it you need to specify a valid
deployment URL. This could be something like:

- scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
- sftp://my.server.com/deployment/dir (for SFTP deployment)
- file:///path/to/deployment/dir (for deploying to a local file
system)

Hope this helps
-Tim

Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
  



Hi,
I  use apache-tomcat-5.5.17 as a server for the project site,the

  
  

url
is
  



http://localhost:8080/pcie/, I have added the configuration in the
pom.xmllike this:

  
   maven
   scp://localhost:8080/pcie/
  
 

I have start up the server successfull as well as I Have execute
"site"
command,but when I execute "site-deploy",I appear the error like
this:
FATAL ERROR: Error executing Maven for a project
org.apache.maven.lifecycle.LifecycleExecutionException: Error
uploading

  
  

site
  



 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:559)
 at


  
  

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
  



(DefaultLifecycleExecutor.java:475)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:454)
 at


  
  

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
  



(DefaultLifecycleExecutor.java:306)
 at

  
  

org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
  



DefaultLifecycleExecutor.java:273)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:140)
 at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java

  
  

:441)
  



 at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java

  
  

:382)
  



 at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error

  
  

uploading
  



site
 at org.apache.maven.plugins.site.SiteDeployMojo.execute(

  
  

SiteDeployMojo.java
  



:184)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:412)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:534)
 ... 8 more
Caused by:

  
  

org.apache.maven.wagon.authentication.AuthenticationException
:
  



Cannot connect. Reason: invalid server's version string
 at

  
  

org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
(
  



AbstractSshWagon.java:239)
 at

  
  

org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
  



 at

  
  

org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
  



 at org.apache.maven.plugins.site.SiteDeployMojo.execute(

  
  

SiteDeployMojo.java
  



:153)
 ... 10 more
Caused by: com.jcraft.jsch.JSchException: invalid server's version

  
  

string
  

 

Re: Can't deploy site,Help please.

[Markku Saarela]

One slash character was dropped out :-)
file:///192.1.1.0/temp/directory

- markku


Markku Saarela wrote:
> Hi,
>
> No, File protocol can deploy any directory in network where user has
> access. The first slash character is defining that path is absolute two
> others are some server delimiters.
>
> file:/c:/temp vs. file:///someserver/depl or even
> file://192.1.1.0/temp/directory
>
> rgds,
> markku
>
> jiangshachina wrote:
>   
>> Hello,
>>   
>> 
>>> I have solved the issue by used file:///path/to/deployment/dir
>>> 
>>>   
>> "file" protocol just deploys to a local path, doesn't it?
>>
>> a cup of Java, cheers!
>> Sha Jiang
>>
>>
>> 秋秋 wrote:
>>   
>> 
>>> Hi,
>>> yes,I have solved the issue by used file:///path/to/deployment/dir*, *
>>> thanks.
>>>
>>>
>>> 2007/2/6, Tim Kettler <[EMAIL PROTECTED]>:
>>> 
>>>   
>>>> Hi,
>>>>
>>>> the URL you give in the distribution management section is the HTTP URL
>>>> of your projects site. To deploy it you need to specify a valid
>>>> deployment URL. This could be something like:
>>>>
>>>> - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
>>>> - sftp://my.server.com/deployment/dir (for SFTP deployment)
>>>> - file:///path/to/deployment/dir (for deploying to a local file system)
>>>>
>>>> Hope this helps
>>>> -Tim
>>>>
>>>> Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
>>>>   
>>>> 
>>>>> Hi,
>>>>> I  use apache-tomcat-5.5.17 as a server for the project site,the
>>>>> 
>>>>>   
>>>> url
>>>> is
>>>>   
>>>> 
>>>>> http://localhost:8080/pcie/, I have added the configuration in the
>>>>> pom.xmllike this:
>>>>> 
>>>>>   
>>>>>maven
>>>>>scp://localhost:8080/pcie/
>>>>>   
>>>>>  
>>>>>
>>>>> I have start up the server successfull as well as I Have execute "site"
>>>>> command,but when I execute "site-deploy",I appear the error like this:
>>>>> FATAL ERROR: Error executing Maven for a project
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
>>>>> 
>>>>>   
>>>> site
>>>>   
>>>> 
>>>>>  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>>>> DefaultLifecycleExecutor.java:559)
>>>>>  at
>>>>>
>>>>> 
>>>>>   
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
>>>>   
>>>> 
>>>>> (DefaultLifecycleExecutor.java:475)
>>>>>  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>>>>> DefaultLifecycleExecutor.java:454)
>>>>>  at
>>>>>
>>>>> 
>>>>>   
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
>>>>   
>>>> 
>>>>> (DefaultLifecycleExecutor.java:306)
>>>>>  at
>>>>> 
>>>>>   
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>>>>   
>>>> 
>>>>> DefaultLifecycleExecutor.java:273)
>>>>>  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>>>>> DefaultLifecycleExecutor.java:140)
>>>>>  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
>>>>> 
>>>>>   
>>>> :441)
>>>>   
>>>> 
>>>>>  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
>>>>> 
>>>>>   
>>>> :382)
>>>>   
>>>> 
>>>>>  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
>>>>> Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>>>>> 
>>>>>   
>>

Re: Can't deploy site,Help please.

[Markku Saarela]

Hi,

No, File protocol can deploy any directory in network where user has
access. The first slash character is defining that path is absolute two
others are some server delimiters.

file:/c:/temp vs. file:///someserver/depl or even
file://192.1.1.0/temp/directory

rgds,
markku

jiangshachina wrote:
> Hello,
>   
>> I have solved the issue by used file:///path/to/deployment/dir
>> 
> "file" protocol just deploys to a local path, doesn't it?
>
> a cup of Java, cheers!
> Sha Jiang
>
>
> 秋秋 wrote:
>   
>> Hi,
>> yes,I have solved the issue by used file:///path/to/deployment/dir*, *
>> thanks.
>>
>>
>> 2007/2/6, Tim Kettler <[EMAIL PROTECTED]>:
>> 
>>> Hi,
>>>
>>> the URL you give in the distribution management section is the HTTP URL
>>> of your projects site. To deploy it you need to specify a valid
>>> deployment URL. This could be something like:
>>>
>>> - scp://my.server.com/var/www/htdocs/myproject (for SSH's secure copy)
>>> - sftp://my.server.com/deployment/dir (for SFTP deployment)
>>> - file:///path/to/deployment/dir (for deploying to a local file system)
>>>
>>> Hope this helps
>>> -Tim
>>>
>>> Am Dienstag, den 06.02.2007, 11:03 +0800 schrieb 秋秋:
>>>   
 Hi,
 I  use apache-tomcat-5.5.17 as a server for the project site,the
 
>>> url
>>> is
>>>   
 http://localhost:8080/pcie/, I have added the configuration in the
 pom.xmllike this:
 
   
maven
scp://localhost:8080/pcie/
   
  

 I have start up the server successfull as well as I Have execute "site"
 command,but when I execute "site-deploy",I appear the error like this:
 FATAL ERROR: Error executing Maven for a project
 org.apache.maven.lifecycle.LifecycleExecutionException: Error uploading
 
>>> site
>>>   
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:559)
  at

 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
>>>   
 (DefaultLifecycleExecutor.java:475)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:454)
  at

 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
>>>   
 (DefaultLifecycleExecutor.java:306)
  at
 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>>>   
 DefaultLifecycleExecutor.java:273)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:140)
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
>>> :441)
>>>   
  at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java
 
>>> :382)
>>>   
  at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
 Caused by: org.apache.maven.plugin.MojoExecutionException: Error
 
>>> uploading
>>>   
 site
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
>>> SiteDeployMojo.java
>>>   
 :184)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:412)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:534)
  ... 8 more
 Caused by:
 
>>> org.apache.maven.wagon.authentication.AuthenticationException
>>> :
>>>   
 Cannot connect. Reason: invalid server's version string
  at
 
>>> org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
>>> (
>>>   
 AbstractSshWagon.java:239)
  at
 
>>> org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143)
>>>   
  at
 
>>> org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:106)
>>>   
  at org.apache.maven.plugins.site.SiteDeployMojo.execute(
 
>>> SiteDeployMojo.java
>>>   
 :153)
  ... 10 more
 Caused by: com.jcraft.jsch.JSchException: invalid server's version
 
>>> string
>>>   
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at com.jcraft.jsch.Session.connect(Unknown Source)
  at
 
>>> org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
>>> (
>>>   
 AbstractSshWagon.java:228)
  ... 13 more


 what can I do?
 
>>> -
>>> 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]

Re: Maven release plugin and J2EE projects

[Markku Saarela]

Configure you release plugin to make install to you local repository 
first, then release:prepare success.


 
   maven-release-plugin
   true
   
 clean install
   
 

- markku

Randy L. Ringeisen wrote:

Hi.  I have a question about the release plugin (Maven 2 release plug-in
2.0 beta 4).  I have a multi-level project as follows
 
Parent - artifact type is POM

   -- Ejb - creates an EJB JAR
   -- Ear - creates an EAR that includes the EJB jar
 
The Ear project depends on the Ejb jar that is created (because it has

to include it in the ear).  This works great until I run mvn
release:prepare.  The problem is that the release plugin modifies the
version number in the POM files from the snapshot version (e.g.
1.0-SNAPSHOT) to the release version (e.g. 1.0).  It then builds the EJB
project but does not install it into the local repository (which makes
sense, since this is the prepare step).  Then it tries to build the EAR
project and fails because the EJB jar which it depends on is not found.
 
The workaround I have been using is to run "mvn release:prepare" until

it fails  By that time it has modified the version number in the POM
files.  Then I run "mvn install" to get the Ejb jar into the local
repository.  Then I can run "mvn release:prepare" again.  It will pick
up where it left off and finish successfully.  After that I can run "mvn
release:perform" and all is right with the world.
 
Does anyone have a more elegant way to solve this problem?


Randy Ringeisen

PS.  Have only been using Maven for a few months and it is great.


  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Release plugin

[Markku Saarela]

Hi,

try using the *preparationGoals* maven-release-plugin in order to do an 
install instead of integration-test:



   <*preparationGoals*>clean install


- markku

Portuendo Vestado wrote:

Hi all,

When using "mvn release:prepare" on an aggregate project, it updates project
and module pom versions to non-SNAPSHOT (1.0.0 vs 1.0.0-SNAPSHOT), and then
fails with a message that one of the module artifacts v. 1.0.0 cannot be
found (which makes sense since they haven't been deployed to local/remote
repositories yet).

Then, as a test, I'm attempting to run "mvn deploy" against the parent
project; and same message shows up. This didn't happen when I wanted to
deploy a snapshot version.

Does that mean I'd have to release each sub-project one-by-one, and not as
part of the parent aggregate project?

Thanks,
P



___ 
O Yahoo! está de cara nova. Venha conferir! 
http://br.yahoo.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]

Re: [m2]maven-source-plugin 2.0.1 infinitive source jar build

[Markku Saarela]

Yes that was the reason. I had LICENCE and NOTICE files in basedir. So 
waiting 2.0.2 version of the plugin :-) .


Markku

Jochen Wiedmann wrote:

On 12/10/06, Markku Saarela <[EMAIL PROTECTED]> wrote:


Yes, but i can't see anything weird. I terminate this job after jar file
size had grown to 4 GB.

[INFO] Preparing source:jar


Most possibly caused by the MSOURCES-6 bug: I bet you have specified a
resource with ${basedir} or "." as the base directory.

For a possible workaround, see

   
http://repo1.maven.org/maven2/org/apache/commons/commons-parent/1/commons-parent-1.pom 



(it uses the antrun plugin to achieve the same purpose).


Jochen





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[m2]maven-source-plugin 2.0.1 infinitive source jar build

[Markku Saarela]

Hi,

I have maven-source-plugin configured in pom to goal jar and when i run 
mvn package command twice without clean the second time caused 
infinitive source jar file build. File size grows to GB's and execution 
must abort. This caused release plugin to hangs the same point. Any ideas?


rgds,

Markku

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2 2.0.4] maven-release-plugin 2.0-beta-4 fails with ejb-client depency type to perform prepare

[Markku Saarela]

Thanks,

That save for manually doing the same thing.

rgds,

Markku

Antonio Parolini wrote:

I had the same issue.

I solved it by using the preparationGolas maven-release-plugin option in
order to do an install instead of integration-test:


clean install


cheers,
-tony 


Markku Saarela-2 wrote:
  
For all ejb-client type depencies in multiproject system fails to 
resolve artifacts:



  varma.yrpro.income
  dbserviceejb
  1.0-SNAPSHOT
  ejb-client


produces error like this:

[INFO] Failed to resolve artifact.

Missing:
--
1) varma.yrpro.income:dbserviceejb:ejb-client:client:1.0

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=varma.yrpro.income 
-DartifactId=dbserviceejb \

  -Dversion=1.0 -Dpackaging=ejb-client -Dfile=/path/to/file

  Path to dependency:
1) varma.yrpro.income:ctrlcommon:ejb:1.0
2) varma.yrpro.income:dbserviceejb:ejb-client:client:1.0

Any ideas solving this problem.

Last wednesday it worked and now it's broken.

- Markku Saarela


-
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]

Re: Tagging a maven project in sourceforge with release:prepare fails with this message

[Markku Saarela]

Thanks,

That resolved also mine release tagging problem at Sourceforge.

Rgds,

Markku

David wrote:

Just in case it's useful for someone, I've found the "curious"
solution to this weird problem within the SF tracker after being
knocking my head against the screen for some time...

http://sourceforge.net/tracker/index.php?func=detail&aid=1599910&group_id=1&atid=21 




David

2006/12/6, David <[EMAIL PROTECTED]>:

Hi,

As you can see, there is a commit in the second line that is executed
perfectly (I have checked it at my svn repository in sourceforge), but
the 4th line which should create a new directory under "tags" for the
release being cooked, fails with a 403  :(

Any clue?

[INFO] Checking in modified POMs...
[INFO] Executing: svn --username nimeacuerdo --password *
--non-interactive commit --file /tmp/maven-scm-523270409.commit
/Users/david/Documents/eclipseworkspace/mavenium/pom.xml
[INFO] Working directory: 
/Users/david/Documents/eclipseworkspace/mavenium

[INFO] Tagging release with the label mavenium-0.1...
[INFO] Executing: svn --username nimeacuerdo --password *
--non-interactive copy --file /tmp/maven-scm-884527461.commit .
https://svn.sourceforge.net/svnroot/mavenium/tags/mavenium-0.1
[INFO] Working directory: 
/Users/david/Documents/eclipseworkspace/mavenium
[INFO] 


[ERROR] BUILD FAILURE
[INFO] 


[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: COPY of mavenium-0.1: 403 Forbidden (https://svn.sourceforge.net)

[INFO] 




TIA



-
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]

Re: AW: maven-changes-plugin help please

[Markku Saarela]

You should use changes plugin it is newer version of that codehaus plugin:

 
   org.apache.maven.plugins
   maven-changes-plugin
   
 ${basedir}/src/site/changes.xml
   
   
 
   
 changes-report
   
 
   
 


[EMAIL PROTECTED] wrote:

Hi
I use


org.codehaus.mojo

changes-maven-plugin
2.0-beta-1




changes-report





works fine!



-Ursprüngliche Nachricht-
Von: Naess, Ronny [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 25. Oktober 2006 10:16
An: Maven Users List
Betreff: Re: maven-changes-plugin help please


 
Does maven-changes-plugin work well with M2 and what version should I

choose? I tried it a while ago without success.
By the way, we use Subversion.

-Ronny

-Opprinnelig melding-
Fra: Dennis Lundberg [mailto:[EMAIL PROTECTED] 
Sendt: 24. oktober 2006 23:15

Til: Maven Users List; [EMAIL PROTECTED]
Emne: Re: maven-changes-plugin help please

The Apache-version of the plugin is a reporting-plugin. This means that
it will generate its output during site generation. It also means that
configuration should be in the  section of your pom. Please
see:
   http://maven.apache.org/plugins/maven-changes-plugin/usage.html

--
Dennis Lundberg

Pete wrote:
  
Help, I'm trying to switch from the old codehaus maven-changes-plugin 
to the new org.apache.maven.plugins version.


Previously I had my pom configured to use the old plugin during the 
compile phase, so that a changes-report.html could be nested inside 
the web app's pages.


Now with the new plugin it doesn't seem to generate a report at all, 
is there something about the new plugin which means it will only 
generate during the 'site' goal ?


I've tried with and without a phase, and -X doesn't show any 
configuration for the plugin happening at all  :-




org.apache.maven.plugins
maven-changes-plugin
2.0-beta-2-SNAPSHOT


produce changes html page


false
   
  



${project.build.outputDirectory}/changes/changes.xml
  




changes-report





changes-report





-
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]


!DSPAM:453e87fd64881357017964!


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  
 

Kabel Deutschland bietet Ihnen Internet, Telefonieren und Fernsehen aus einer Hand. Informieren Sie sich über unsere Produkte unter 


www.kabeldeutschland.de
 
Diese E-Mail und etwaige Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind, benachrichtigen Sie bitte den Absender und vernichten Sie anschließend diese Mail und die Anlagen.



-
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]

Re: [m204] want to deploy site to local hard drive withouth scm

[Markku Saarela]

First you must run mvn site:site and after that mvn site:deploy

- markku

Mick Knutson wrote:

And then mvn site:deploy:


c:\opt\npi>mvn site:deploy
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   npi
[INFO]   common
[INFO]   common-jar
[INFO]   properties-configuration
[INFO]   common-war
[INFO]   project-web
[INFO]   npi-webproject
[INFO]   project-ear
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO]
 


[INFO] Building npi
[INFO]task-segment: [site:deploy]
[INFO]
 


[INFO] [site:deploy]
file:///c:/stage - Session: Opened
file:///c:/stage - Session: Disconnecting
file:///c:/stage - Session: Disconnected
[INFO]
 


[INFO] Building common
[INFO]task-segment: [site:deploy]
[INFO]
 


[INFO] [site:deploy]


This created a directory called "C:\stage\stage\localhost" but there 
were no

files in it.



On 9/19/06, Mick Knutson <[EMAIL PROTECTED]> wrote:


Embedded error:
c:\opt\npi\target\site\stage\localhost\c:\opt\fullsite\integration.html 
(The

filename, directory name, or volume label syntax is incorrect)


Thsi was with mvn site:stage and this declaration:



delta-npi-site
Delta NPI Web
 file:///c:/opt/fullsite






On 9/18/06, franz see < [EMAIL PROTECTED]> wrote:
>
>
>
>
> Markku Saarela wrote:
> >
> > Put your parent pom.xml site configuration using file protocol
> >
> >   
> > 
> >   website
> >   file:///c:/stage 
> > 
> >   
> >
> > - markku
> >
> > Mick Knutson wrote:
> >> How can I deploy, and/or stage my entire site (including 
sub-modules)

>
> >> locally to c:\stage
> >>
> >
> >
> > 
-

> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> Good day to you, Mick,
>
> For more info, you can also take a look at [1] and go to the 
"Staging a
> Site" section. However, [1] has not yet been released. Thus, if you 
have

> any
> comments or suggestions, please feel free to let us know about it so
> that we
> can improve it.
>
> Thanks,
> Franz
>
> [1] 
http://people.apache.org/~oching/maven-site-plugin/usage.html<http://people.apache.org/%7Eoching/maven-site-plugin/usage.html> 


> --
> View this message in context:
> 
http://www.nabble.com/-m204--want-to-deploy-site-to-local-hard-drive-withouth-scm-tf2293502.html#a6382567 


> 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

DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m204] want to deploy site to local hard drive withouth scm

[Markku Saarela]

Put your parent pom.xml site configuration using file protocol

 
   
 website
 file:///c:/stage
   
 

- markku

Mick Knutson wrote:

How can I deploy, and/or stage my entire site (including sub-modules)
locally to c:\stage




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: J2EE Client Application JAR is not detected as J2EE module

[Markku Saarela]

Actually application-client is part of J2EE specification. See section 
of Application clients J2EE 1.4 spec section 9.7 J2EE Application Client 
XML Schema.


Ant has targets that can create these Application client artifacts.

I also favor for building application client jar for Swing applications 
with Maven2.


Regards,

Markku

Alexander Sack wrote:
I'm pretty sure the "J2EE client application descriptor" you speak of 
is a
BEA only primitive and not generic enough to be included in the EAR 
plugin

(please correct me if I'm wrong, I don't remember ever seeing this in the
J2EE spec).

With that said a light bult has sort of went off and perhaps the EAR 
plugin
should have a PLATFORM identifier that can fine tune the packaging 
based on
Java EE app server.  As anyone who has worked with more than one app 
server
knows, the spec has A LOT of room for interpretation and some 
platforms just

aren't compliant (either they choose to be or are catching up).

Good idea, bad idea?

-aps

On 9/15/06, Wayne Fay <[EMAIL PROTECTED]> wrote:


If the current release of the EAR plugin does not support the
functionality you desire, you have a few options:

1. Complain about missing functionality on the Maven User list.
2. File a JIRA Enhancement report and hope someone looks at your issue
and decides it is worth spending some time to implement for you.
3. Write the code yourself, then file a JIRA with your changes
attached and wait for it to be incorporated into the released code
which will take some time to actually land in a non-snapshot repo
(several weeks at a minimum).

Pick one from above and do it. In the mean time, if you want things to
work, you will need to be practical about things -- simply add the
entry into the application.xml (or whatever file, I'm not familiar
with J2EE Client Apps) manually or in the pom.xml and move on with
life.

Wayne

On 9/15/06, Markus KARG <[EMAIL PROTECTED]> wrote:
> No I do not mean ejb-client but "J2EE Client Application":
> What you mean is a JAR containing the interfaces of the EJBs, but 
what I
> mean is a standalone ("Swing") application that is to be run inside 
of a

> "J2EE Client Container".
>
> I have seen that EJB-JARs are enlistet in the EAR's application.xml
> automatically, and we want this to happen with the "J2EE Client
> Application" also, without adding it to the EAR's pom.xml manually. 
This

> should be possible since a "J2EE Client Application" always contains a
> file named META-INF\client-application-xml, so the EAR task just 
need to

> look into the JAR to find out about its type. I do not understand why
> this has to be specified manually.
>
> Thanks
> Markus
>
> Stephane Nicoll schrieb:
>
> > you mean ejb-client? Your dependency should be 'ejb-client' not 
'jar'.

> >
> > Anyhow, if you want a jar to be included in the application.xml, 
just

> > configure the plugin acccordingly (includeInApplicationXml) [1]
> >
> > Cheers,
> > Stéphane
> >
> > [1] http://maven.apache.org/plugins/maven-ear-plugin/howto.html
> >
> > On 9/15/06, Markus KARG <[EMAIL PROTECTED]> wrote:
> >
> >> I am using the EAR packaging to let Mvn2 create an .ear file plus
> >> automatically create an application.xml inside of it.
> >> It detects all my EJB modules, but it doesn't detect that one of 
the

> >> included JARs is not a utility JAR but in fact a "J2EE Client
> >> Application JAR".
> >> Maybe the packaging type I have used for that JAR is wrong (I used
JAR
> >> since I thought the EAR packager will detect the contained
> >> client-application.xml file).
> >> So what is the correct way to specify "J2EE Client Application JAR"
> >> packaging instead of simple utility "JAR" packaging?
> >>
> >> Thanks a lot!
> >> Markus
> >>
> >>
> >>
> >
> >
>
>
>

-
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]

Re: EJB Client JAR

[Markku Saarela]

And you can config this ejb client jar with |clientExcludes parameter in 
|maven-ejb-plugin as documented here: 
http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html


Regards,

Markku

Markus KARG wrote:

Markku,

thanks a lot for your kind help!

We will try out tomorrow!

Thanks a lot
Markus

Markku Saarela wrote:
  

Configure you ejb plugin like this:

 
   
 
   maven-ejb-plugin
   true
   
 
   
 true
   
 
 true
   
 
   
 

then in you module where you have dependency of this ejb client jar :

 
   
 your_group_id
 dbserviceejb
 ${version}
 ejb-client
   
 

regards,

Markku


Markus KARG wrote:


Actually I don't want to do that but I want to know and do the
maven-ejb-plugin way.

Nevertheless,
thanks a lot!

Markus

[EMAIL PROTECTED] schrieb:

  

Not necessarily the maven-ejb-plugin way, but you can create a separate
module for the EJB client and then add a compile dependency on the that
project in your EJB project's pom.  We did this to get around the fact
that using the generateClient option on the maven-ejb-plugin
generates a
pom for the client with way too many dependencies (includes all of the
EJBs dependencies) and so that we could compile the EJB in 1.5 but
compile the client under 1.4.


-Original Message-
From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Thursday,
September 14, 2006 4:23 AM
To: Maven Users List
Subject: EJB Client JAR

Using Maven2's ejb package, I was able to create an ejb-jar from my
sources.
But not I want Maven to create an "EJB Client JAR", that only contains
the interfaces, and make another JAR dependent of that "EJB Client
JAR" (by means of Class-Path: entry in MANIFEST.MF).

How to do that?
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





  

Re: EJB Client JAR

[Markku Saarela]

Configure you ejb plugin like this:

 
   
 
   maven-ejb-plugin
   true
   
 
   
 true
   
 
 true
   
 
   
 

then in you module where you have dependency of this ejb client jar :

 
   
 your_group_id
 dbserviceejb
 ${version}
 ejb-client
   
 

regards,

Markku


Markus KARG wrote:
Actually I don't want to do that but I want to know and do the 
maven-ejb-plugin way.


Nevertheless,
thanks a lot!

Markus

[EMAIL PROTECTED] schrieb:


Not necessarily the maven-ejb-plugin way, but you can create a separate
module for the EJB client and then add a compile dependency on the that
project in your EJB project's pom.  We did this to get around the fact
that using the generateClient option on the maven-ejb-plugin generates a
pom for the client with way too many dependencies (includes all of the
EJBs dependencies) and so that we could compile the EJB in 1.5 but
compile the client under 1.4.


-Original Message-
From: Markus KARG [mailto:[EMAIL PROTECTED] Sent: Thursday, 
September 14, 2006 4:23 AM

To: Maven Users List
Subject: EJB Client JAR

Using Maven2's ejb package, I was able to create an ejb-jar from my
sources.
But not I want Maven to create an "EJB Client JAR", that only contains
the interfaces, and make another JAR dependent of that "EJB Client 
JAR" (by means of Class-Path: entry in MANIFEST.MF).


How to do that?
 






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

M2 release:prepare fails with Subversion to tag SCM reason: Source url is from different repository

[Markku Saarela]

Hi,

We are using Maven2 2.0.4 with Subversion 1.3 and now we can't make 
anymore releases. Previously we success.


Here is snippet from parent pom.xml

 
   scm:svn:svn://fitst37/income/trunk
   
scm:svn:svn://fitst37/income/trunk

 

 
   maven-release-plugin
   
 saarfmar
 12345
   
 

Here is output:

[INFO] [release:prepare]
[INFO] Resuming release from phase 'scm-tag'
[INFO] Tagging release with the label 1.0.0...
[INFO] Executing: svn --non-interactive copy --file 
C:\DOCUME~1\saarfmar\LOCALS~1\Temp\maven-scm-108

0661760.commit . svn://fitst37/income/tags/1.0.0
[INFO] Working directory: C:\temp\income
[INFO] 


[ERROR] BUILD FAILURE
[INFO] 


[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different 
repository


[INFO] 


[DEBUG] Trace
org.apache.maven.BuildFailureException: Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: Source url 'svn://[EMAIL PROTECTED]/income/trunk' is from different 
repository


   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor

.java:555)

Anyone have any idea what do to?

Regards,

Markku Saarela

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[m2 2.0.4] maven-release-plugin 2.0-beta-4 fails with ejb-client depency type to perform prepare

[Markku Saarela]

For all ejb-client type depencies in multiproject system fails to 
resolve artifacts:


   
 varma.yrpro.income
 dbserviceejb
 1.0-SNAPSHOT
 ejb-client
   

produces error like this:

[INFO] Failed to resolve artifact.

Missing:
--
1) varma.yrpro.income:dbserviceejb:ejb-client:client:1.0

 Try downloading the file manually from the project website.

 Then, install it using the command:
 mvn install:install-file -DgroupId=varma.yrpro.income 
-DartifactId=dbserviceejb \

 -Dversion=1.0 -Dpackaging=ejb-client -Dfile=/path/to/file

 Path to dependency:
   1) varma.yrpro.income:ctrlcommon:ejb:1.0
   2) varma.yrpro.income:dbserviceejb:ejb-client:client:1.0

Any ideas solving this problem.

Last wednesday it worked and now it's broken.

- Markku Saarela


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

M2 release plugin snapshot version does not handle new development depency version correctly in multimodule project

[Markku Saarela]

Hi,

After release:perform snapshot version project pom.xml include 
dependency versions for dependent projects remains to new release 
version ex. 1.0a not new development version ex 1.0-SNAPSHOT. I couldn't 
find anything from google concerning  this issue. Is there any way to 
avoid this. It's annoying because there are over 40 modules in project.


Regards, Markku Saarela

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: m2 release:prepare fails to build subproject that depends previously builded ejb projects

[Markku Saarela]

Hi,

I resolved this problem. Earlier in m2 when you include dependency with 
type ejb to project and that project was included to another ear project 
than were this dependent project is originally located also this another 
ear get this dependency ejb project as it's ejb module. So when you 
install these two ear's to same server the second one couldn't install 
because there was allready same ejb installed.


Now it looks like these depencies is resolved correctly and i was  able 
to chance dependency type back to ejb and then release work again :-).


- markku

[EMAIL PROTECTED] wrote:

Hi,

All missed artifacts are ejb projects which dependency type is jar.
Normal jar projects it success to resolve. Earlier in this summer we
were able to succesfully complete making releases. Pom's are unchanged.

We are little bit hurry on this release. 


Regards,

Markku Saarela

Here some stack on this failure:

[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 4 source files to
C:\Files\TE\varma\income\registrationinvoiceejb\target\classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [ejb:ejb]
[INFO] Building ejb registrationInvoice-0.9.6
[INFO] Building jar:
C:\Files\TE\varma\income\registrationinvoiceejb\target\registrationInvoi
ce-
0.9.6.jar
[INFO] Building ejb client registrationInvoice-0.9.6-client
[INFO] Building jar:
C:\Files\TE\varma\income\registrationinvoiceejb\target\registrationInvoi
ce-
0.9.6-client.jar
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: default}]
[INFO] Building jar:
C:\Files\TE\varma\income\registrationinvoiceejb\target\registrationInvoi
ce-
0.9.6-sources.jar
[INFO]


[INFO] Building Control Common
[INFO]task-segment: [clean, integration-test]
[INFO]


[INFO] [clean:clean]
[INFO] Deleting directory C:\Files\TE\varma\income\ctrlcommon\target
[INFO] Deleting directory
C:\Files\TE\varma\income\ctrlcommon\target\classes
[INFO] Deleting directory
C:\Files\TE\varma\income\ctrlcommon\target\test-classes
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://fitst62:8080/yrpro/maven2/varma/yrpro/income/customerservicesejb/
0.9.6/custo
merservicesejb-0.9.6.jar
[WARNING] Unable to get resource from repository corporate
(http://fitst62:8080/yrpro/maven2)
Downloading:
http://repo1.maven.org/maven2/varma/yrpro/income/customerservicesejb/0.9
.6/customer
servicesejb-0.9.6.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://fitst62:8080/yrpro/maven2/varma/yrpro/income/dbserviceejb/0.9.6/d
bserviceejb
-0.9.6.jar
[WARNING] Unable to get resource from repository corporate
(http://fitst62:8080/yrpro/maven2)
Downloading:
http://repo1.maven.org/maven2/varma/yrpro/income/dbserviceejb/0.9.6/dbse
rviceejb-0.
9.6.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://fitst62:8080/yrpro/maven2/varma/yrpro/income/registrationInvoice/
0.9.6/regis
trationInvoice-0.9.6.jar
[WARNING] Unable to get resource from repository corporate
(http://fitst62:8080/yrpro/maven2)
Downloading:
http://repo1.maven.org/maven2/varma/yrpro/income/registrationInvoice/0.9
.6/registra
tionInvoice-0.9.6.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
Downloading:
http://fitst62:8080/yrpro/maven2/varma/yrpro/income/registration/0.9.6/r
egistration
-0.9.6.jar
[WARNING] Unable to get resource from repository corporate
(http://fitst62:8080/yrpro/maven2)
Downloading:
http://repo1.maven.org/maven2/varma/yrpro/income/registration/0.9.6/regi
stration-0.
9.6.jar
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Missing:
--
1) varma.yrpro.income:customerservicesejb:jar:0.9.6

  Try downloading the file manually from the project website.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma