Re: maven depdendency:tree not working right?

2011-11-10 Thread Ioan Eugen Stan
2011/11/10 Ioan Eugen Stan :
> Hi,
>
> I'm running
> mvn dependency:tree -DoutputType=graphml
>
> on Apache James and I'm getting an output like this:
>
> [INFO] 
> 
> [INFO] Building Apache James Server Client 3.0-beta4-SNAPSHOT
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ james-server-cli 
> ---
> [INFO] org.apache.james:james-server-cli:jar:3.0-beta4-SNAPSHOT
> [INFO] +- 
> org.apache.james:james-server-data-api:jar:3.0-beta4-SNAPSHOT:compile
> [INFO] |  +- org.apache.james:apache-mailet:jar:2.4:compile
> [INFO] |  \- javax.mail:mail:jar:1.4.4:compile
> [INFO] +- commons-cli:commons-cli:jar:1.2:compile
> [INFO] \- junit:junit:jar:3.8.1:test
> [INFO] 
> 
>
>
> Shouldn't I get GraphML output? Also tried with dot and other stuf.
> Still the same output. What am I doing wrong?
> I'm trying to get the dependency tree of James.
>
> I'm using:
>
> mvn --version
> Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> Default locale: ro_RO, platform encoding: UTF-8
> OS name: "linux", version: "3.0.0-1-amd64", arch: "amd64", family: "unix"
>
> Thanks,
>
> --
> Ioan Eugen Stan
> http://ieugen.blogspot.com/
>

SOLVED: added the plugin to pom.xml and forced version to 2.3. like:

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


It seams that maven uses a lower version by default and that graphML
is only available in that version.

-- 
Ioan Eugen Stan
http://ieugen.blogspot.com/

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



maven depdendency:tree not working right?

2011-11-10 Thread Ioan Eugen Stan
Hi,

I'm running
mvn dependency:tree -DoutputType=graphml

on Apache James and I'm getting an output like this:

[INFO] 
[INFO] Building Apache James Server Client 3.0-beta4-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ james-server-cli ---
[INFO] org.apache.james:james-server-cli:jar:3.0-beta4-SNAPSHOT
[INFO] +- org.apache.james:james-server-data-api:jar:3.0-beta4-SNAPSHOT:compile
[INFO] |  +- org.apache.james:apache-mailet:jar:2.4:compile
[INFO] |  \- javax.mail:mail:jar:1.4.4:compile
[INFO] +- commons-cli:commons-cli:jar:1.2:compile
[INFO] \- junit:junit:jar:3.8.1:test
[INFO] 


Shouldn't I get GraphML output? Also tried with dot and other stuf.
Still the same output. What am I doing wrong?
I'm trying to get the dependency tree of James.

I'm using:

mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
Default locale: ro_RO, platform encoding: UTF-8
OS name: "linux", version: "3.0.0-1-amd64", arch: "amd64", family: "unix"

Thanks,

-- 
Ioan Eugen Stan
http://ieugen.blogspot.com/

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



javadoc standard doclet

2011-09-21 Thread Ioan Eugen Stan
Hello,

Could you please tell me what is the standard doclet used by Maven
javadco plugin in case no  is specified?

I'm trying to use APIviz for Apache James, but it fails for pom
packaged projects (James has a lot of components and uses inheritance
and aggregation extensively). It fails because it can't find the
target/classes directory, since pom packaged projects don't have
classes to compile. (APIviz needs classes to make diagrams) .

The solution that I have came up to is to store a configured JavaDoc
plgin in the plugin management of the parent pom (james-parent) with
doclet set to APIviz and overwrite this in pom packaged projects by
declaring doclet to be standard again so it will not fail.

You can find the original discussion at [1].


[1] http://www.mail-archive.com/server-dev@james.apache.org/msg35801.html

Thanks,

-- 
Ioan Eugen Stan
http://ieugen.blogspot.com/

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



RE: Custom tags in the pom

2011-03-30 Thread Stan Devitt
Either it is an xml document or it is not.  The fact remains that xml name 
spaces were designed specifically to deal with this situation.  Trying to 
re-implement the feature based on comments and/or PI's seems kind of risky and 
certainly without general tooling support :)

Stan

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Wednesday, March 30, 2011 12:15 PM
To: Maven Users List
Cc: Stan Devitt
Subject: Re: Custom tags in the pom

Modello may object to some uses of namespaces... suck it and see!

On 30 March 2011 16:56, Stan Devitt  wrote:
> Why not name spaces?
>
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Wednesday, March 30, 2011 9:48 AM
> To: Maven Users List
> Subject: Re: Custom tags in the pom
>
> how about XML PI's
>
> IIRC maven tools which rewrite the pom might strip them out, but
> otherwise you'd be fine
>
> On 30 March 2011 14:06, Phillip Hellewell  wrote:
>> Is there any way short of recompiling Maven to allow custom tags in the 
>> pom.xml?
>>
>> Specifically, I would like to have a special tag inside .
>> It's ok if Maven ignores it; I will just look at it from my plugin
>> that will parse the pom manually if it has to.
>>
>> Thanks,
>> Phillip
>>
>> -
>> 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
>
>
> -
> This transmission (including any attachments) may contain confidential 
> information, privileged material (including material protected by the 
> solicitor-client or other applicable privileges), or constitute non-public 
> information. Any use of this information by anyone other than the intended 
> recipient is prohibited. If you have received this transmission in error, 
> please immediately reply to the sender and delete this information from your 
> system. Use, dissemination, distribution, or reproduction of this 
> transmission by unintended recipients is not authorized and may be unlawful.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: Custom tags in the pom

2011-03-30 Thread Stan Devitt
Why not name spaces?

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Wednesday, March 30, 2011 9:48 AM
To: Maven Users List
Subject: Re: Custom tags in the pom

how about XML PI's

IIRC maven tools which rewrite the pom might strip them out, but
otherwise you'd be fine

On 30 March 2011 14:06, Phillip Hellewell  wrote:
> Is there any way short of recompiling Maven to allow custom tags in the 
> pom.xml?
>
> Specifically, I would like to have a special tag inside .
> It's ok if Maven ignores it; I will just look at it from my plugin
> that will parse the pom manually if it has to.
>
> Thanks,
> Phillip
>
> -
> 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


-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: How to release a single module in a Mercurial repository?

2011-03-06 Thread Stan Devitt
What about perforce or clearcase ?

-Original Message-
From: Mark Struberg [mailto:strub...@yahoo.de]
Sent: Sunday, March 06, 2011 4:40 PM
To: Maven Users List
Subject: Re: How to release a single module in a Mercurial repository?

hmm, I think we should remove this Exception.
tagging a subdirectory is again only valid in very special SCMs, mainly SVN 
(don't remember how this did behave in CVS anymore).


Usually a tag is a 'name' on a certain snapshot in the whole repo. Tagging a 
repo will just give you this unique snapshot over the repo, regardless of the 
submodule you are currently in. That's a well known behaviour lots of SCMs and 
most people who are using those SCMs should certainly be aware of it.

LieGrue,
strub

--- On Sun, 3/6/11, Andreas Ebbert-Karroum 
 wrote:

> From: Andreas Ebbert-Karroum 
> Subject: Re: How to release a single module in a Mercurial repository?
> To: "Maven Users List" 
> Cc: "Olivier Lamy" 
> Date: Sunday, March 6, 2011, 8:15 PM
> Hi Oliverm
>
> 2011/3/5 Olivier Lamy 
>
> > @Andreas
> >
> > I see you are using scm 1.4
> >
> > 
> >   org.apache.maven.scm
> >   maven-scm-provider-hg
> >   1.4
> > 
> >
> > Can you try with 1.5-SNAPSHOT ?
> >
>
>
> Yes, I am using the 1.4 release, because the 1.5-Snapshot
> gave an error
> message, that it cannot tag subdirectories of the
> repository. Quote from the
> E-Mail:
>
> The new dependencies with the snapshot release plugin also
> updates to a
> newer hg scm provider. The new hg scm provider has the
> interesting new habit
> to throw an exception, when you want to tag something,
> which does not
> concern the whole repository.
>
> Caused by: org.apache.maven.scm.ScmException: This provider
> doesn't support
> tagging subsets of a directory
>         at
> org.apache.maven.scm.provider.hg.command.tag.HgTagCommand.executeTagCommand(HgTagCommand.java:77)
>         at
> org.apache.maven.scm.command.tag.AbstractTagCommand.executeCommand(AbstractTagCommand.java:81)
>         at
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
>         ... 29 more
>
> --
> Mit freundlichen Grüßen / Best regards
>
> Andreas Ebbert-Karroum | Bereichsleiter der Agilen Software
> Factory
>
> codecentric AG | Merscheider Straße 1 | 42699 Solingen |
> Deutschland
> tel: +49 (0) 212.23362825 | fax: +49 (0) 212.23362879 |
> mobil: +49 (0)
> 175.2664109
> www.codecentric.de | blog.codecentric.de |
> www.meettheexperts.de |
> www.more4fi.de
>
> Sitz der Gesellschaft: Düsseldorf | HRB 63043
> Vorstand: Klaus Jäger (Vorsitzender) | Mirko Novakovic .
> Rainer Vehns
> Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Bernd
> Klinkmann . Jürgen
> Schütz
>
> Diese E-Mail einschließlich evtl. beigefügter Dateien
> enthält vertrauliche
> und/oder rechtlich geschützte Informationen. Wenn Sie
> nicht der richtige
> Adressat sind oder diese E-Mail irrtümlich erhalten haben,
> informieren Sie
> bitte sofort den Absender und löschen Sie diese E-Mail und
> evtl. beigefügter
> Dateien umgehend. Das unerlaubte Kopieren, Nutzen oder
> Öffnen evtl.
> beigefügter Dateien sowie die unbefugte Weitergabe dieser
> E-Mail ist nicht
> gestattet.
>




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


-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



Re: [Maven Shell] - How to upgrade from maven 3.0-alpha-6 to maven 3.0

2010-10-23 Thread Stan
Thanks a lot you both.



Le 23 octobre 2010 23:21, Arnaud Héritier  a écrit :

> 0.11-SNAPSHOT was updated to include it :
>
>
> http://repository.sonatype.org/content/repositories/snapshots/org/sonatype/maven/shell/mvnsh-assembly/0.11-SNAPSHOT/
>
> Arnaud
>
> On Oct 23, 2010, at 11:10 PM, Stan wrote:
>
> > Hello,
> >
> > I tried to upgrade from *maven 3.0-alpha-6* to *maven 3.0* within *maven
> > shell*.
> > I copied all the jar files from *apache-maven-3.0\lib* to
> *mvnsh-0.10\lib*
> > And I removed all **alpha*.jar*
> >
> > When I execute a maven command in the maven shell, I get the following
> > exception:
> >
> > *java.lang.IllegalAccessError: class
> > org.sonatype.maven.shell.maven.internal.ConsoleMavenTransferListener
> cannot
> > access its superclass org.apache.maven.cli.AbstractMavenTransferListener*
> >
> > I checked that these classes are in the jar files.
> >
> > Did anyone meet the same problem and solve it?
> >
> > Thanks.
> > Stan.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


[Maven Shell] - How to upgrade from maven 3.0-alpha-6 to maven 3.0

2010-10-23 Thread Stan
Hello,

I tried to upgrade from *maven 3.0-alpha-6* to *maven 3.0* within *maven
shell*.
I copied all the jar files from *apache-maven-3.0\lib* to *mvnsh-0.10\lib*
And I removed all **alpha*.jar*

When I execute a maven command in the maven shell, I get the following
exception:

*java.lang.IllegalAccessError: class
org.sonatype.maven.shell.maven.internal.ConsoleMavenTransferListener cannot
access its superclass org.apache.maven.cli.AbstractMavenTransferListener*

I checked that these classes are in the jar files.

Did anyone meet the same problem and solve it?

Thanks.
Stan.


RE: standardized Maven GAV URN?

2010-07-01 Thread Stan Devitt
Such a notation would be much more useful if it were

1. standardized and
2. unambiguous

My personal preference would be "something like"

groupId:artifactId(classifier):version;extension[scope]

This way, the classifier, the extension, and the scope could be optional 
simplifying this to

groupId:artifactId:version(defaulting to no classifier, 
extension=jar, scope=compile)

Examples:

junit:junit:3.8.1
junit:junit():3.8.1
junit:junit:3.8.1;jar
junit:junit:3.8.1;[compile]
junit:junit:3.8.1;jar[compile]
junit:junit():3.8.1;jar[compile]

Whatever is done, having multiple conflicting ambiguous versions of this is 
just bad design.  The final choice should probably be consistent with the URI 
specification http://labs.apache.org/webarch/uri/rfc/rfc3986.html   (in this 
case, a path with scheme=GAV, a blank authority, and no query or fragment)  .  
It should be registered.

i.e., GAV:junit:junit:3.8.1

Stan

PS.  The full set of coordinates falls into two categories:

1. name the artifact  (group,artifact,version,classifier)
2. meta-data about the artifact
- assistance to help find it in a repo  (extension)
- restrict its use  (scope)

Here, I have deliberately separated (1) from (2) by a ";"

> Luke Patterson wrote:
> I was looking more for a URN for Maven coordinates, which is slightly
> different than the flattened form of  elements.  e.g. the
>  portion isn't part of what I'm looking for, it is more a statement
> of how I rely upon it

>> Brian Fox-3 wrote:
>> Group:artifact:version:classifier:extension is pretty common
>>



-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: standardized Maven GAV URN?

2010-06-30 Thread Stan Devitt
Why would the recommended format here be different than the format used by the 
dependency plugin?

(e.g.  junit:junit:jar:3.8.1:test )

Stan



-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Monday, June 28, 2010 9:56 PM
To: Maven Users List
Subject: Re: standardized Maven GAV URN?

Group:artifact:version:classifier:extension is pretty common


On Jun 26, 2010, at 1:39 PM, lukewpatterson  wrote:

>
> It would be nice to be able to represent any Maven GAV in a string.  Does
> such a standard exist?
>
> A good use case is for plugins that allow input configuration file paths.
> If there was a reusable component that took an ArtifactResolver and a
> String, then any plugins that currently accept file locations as Strings
> could passively add GAV capability.
>
> e.g. with Clover plugin, I can give the path for the license file, but if I
> want to store the license in the company's internal Maven repo (and thus get
> the advantage of Maven versioning), I have to jump through some dependency
> plugin hoops to get it in the right place at the right time.  I'd like to be
> able to just give the Clover plugin a GAV URN and have it download what it
> needs
>
>
> --
> View this message in context: 
> http://maven.40175.n5.nabble.com/standardized-Maven-GAV-URN-tp511480p511480.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


-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: webResources not copied during build on UNIX.

2010-06-28 Thread Stan Devitt
Is there any possibility that on Windows you are relying on the fact that there 
is no case distinction in the names and using different capitalization?

Stan


-Original Message-
From: Michael Delaney [mailto:mdela...@upromise.com]
Sent: Friday, June 25, 2010 1:40 PM
To: users@maven.apache.org
Subject: webResources not copied during build on UNIX.

All,

I have a war project (by this I mean packaging type is 'war') that, in
the maven-war-plugin, I'm defining some web resources (see snipped
below). During a build on Windows the resources specified in the
'webResources' tag are copied over but during a build on UNIX (most
explicitly Solaris) the resources are not copied over. The paths do not
contain any Windows specific slashes and the case of the files is also
correct.

Anyone know what could be causing this?

We're using maven-war-plugin version 2.1-alpha-1 and
maven-resources-plugin 2.3.


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



false
${basedir}/src/main/resources/templates


web.xml

WEB-INF/templates







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


-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: How to run Exec Maven plugin for each file in a directory?

2009-05-26 Thread Stan Devitt
One way to attach this to (say) the process-resources phase is:


org.codehaus.groovy.maven
gmaven-plugin
1.0-rc-3



generate-sources


execute


  
  
  





Of course, replace the text of the process command line by the command
of your choice, an ant exec task, or just invoke the java class directly
providing that a suitable jar is in the plugin dependency list.

Stan.

-Original Message-
From: janszm [mailto:me...@jansz.com]
Sent: Tuesday, May 26, 2009 9:25 AM
To: users@maven.apache.org
Subject: How to run Exec Maven plugin for each file in a directory?


I have a java program which takes an input-file and output-file as
parameters. I need to run this for a set of files in a directory.

How can I best achieve this with Maven? I have looked at the Exec Maven
plugin and as per http://mojo.codehaus.org/exec-maven-plugin/usage.html
I
can use this to run once. How do I use Maven to run this multiple times
for
all the files in a directory?

I have googled but cant find any info on how to do this, apart from some
posts about using Jelly, but this seems to be no longer supported in the
latest Maven version.

Help appreciated.

Cheers,
Menno
--
View this message in context:
http://www.nabble.com/How-to-run-Exec-Maven-plugin-for-each-file-in-a-di
rectory--tp23722927p23722927.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


-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: Looking for advice on unraveling a particularly nasty Ant->Maven migration

2009-04-24 Thread Stan Devitt
Can you move D to A and use an assembly to build the external jar you
want?



-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: Challenge: Find a plugin combo that achieves what 4 lines of bash script can do...

2009-04-24 Thread Stan Devitt
Note that there is a  <<  in the code to append to a file.

-Original Message-
From: gret...@gmail.com [mailto:gret...@gmail.com] On Behalf Of Grant
Rettke
Sent: Thursday, April 23, 2009 5:24 PM
To: Maven Users List
Subject: Re: Challenge: Find a plugin combo that achieves what 4 lines
of bash script can do...

On Thu, Apr 23, 2009 at 4:13 PM, Martin Gainty 
wrote:
> CDATA is character data
> instructs the parser to leave everything inside [] alone
> http://en.wikipedia.org/wiki/CDATA

The demo code doesn't use it. Have you found that the code gets mucked
with?

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


-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: Challenge: Find a plugin combo that achieves what 4 lines of bash script can do...

2009-04-24 Thread Stan Devitt
The  <[CDATA[  ]]>  bracketing simply tells the xml parser to read the 
enclosed text as raw text.  This allows you to use embedded characters like < 
and >, and is quite handy when the text is code fragments which can contain a 
lot of these special characters.  (It allows you to cut and paste into XML.)

The resulting parsed xml document is identical whether you use entities to 
escape individual characters or use CDATA.

If your program writes the document out again, the CDATA will be gone and the 
corresponding text in the resulting document will escape individual characters 
with  entities like > and <.

Stan
-Original Message-
From: gret...@gmail.com [mailto:gret...@gmail.com] On Behalf Of Grant Rettke
Sent: Thursday, April 23, 2009 4:39 PM
To: Maven Users List
Subject: Re: Challenge: Find a plugin combo that achieves what 4 lines of bash 
script can do...

On Thu, Apr 23, 2009 at 11:03 AM, Stan Devitt  wrote:
>           
>               org.codehaus.groovy.maven
>               gmaven-plugin
>               
>                
>                 generate-resources
>                 
>                   execute
>                 
>                 
>                   
>                   
>                   
>                 
>                
>               
>           

http://groovy.codehaus.org/GMaven+-+Executing+Groovy+Code#GMaven-ExecutingGroovyCode-ExecuteanInlineGroovyScript

Why is the CDATA in there?

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


-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: Challenge: Find a plugin combo that achieves what 4 lines of bash script can do...

2009-04-23 Thread Stan Devitt
One of the nice things about maven projects is that you download them
and they just work.

Assuming the dictionary source files are already broken down by letters
of the alphabet, then the following 5 lines of code does most of it.
(Note that the sed scripts are pretty close to just a line by line
trim() and, of course, you may need to sort the file names.)



   
   org.codehaus.groovy.maven
   gmaven-plugin
   

 generate-resources
 
   execute
 
 
   
   
   
 

   
   


Stan

-
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

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



RE: Release plugin woes

2008-12-07 Thread Stan Devitt
The following work around may help:

1) In the folder containing all the modules add an aggegrator pom that
has one module - the parent of the flat structure.
2) Add the information needed by the release (release plugin, scm info,
etc.) to that pom.
3) Do your release from that pom.

It needs no other interaction with your project. It does not even need
to be the parent of the projects parent pom. The entire project is still
configured/managed from the parent pom in the flat structure and is
unaware of this extra aggregator pom - i.e., no changes.

Stan Devitt


-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] 
Sent: Sunday, December 07, 2008 8:48 AM
To: Maven Users List
Subject: Re: Release plugin woes

there are several issues already opened for the support of flat projects
in the release plugin.
In a flat maven multiproject you have to define the scm part in each
pom.
you have also to do it for the site distribution The release plugin
isn't able to compute the location of the module in the scm with a flat
multiproject What is the constraint which doesn't allow you to have a
hierarchical multiproject ?

On Wed, Dec 3, 2008 at 1:41 PM, <[EMAIL PROTECTED]> wrote:

> Hi!
>
>
> I've in severe trouble with releasing a CVS based flat maven
multiproject:
>
>
> Structure:
>
>  
>../JEEFrameworkRefAppJAVA
>../JEEFrameworkRefAppEJB
>../JEEFrameworkRefAppWAR
>../JEEFrameworkRefAppEAR
>
>
>
> Yes - having it this way is not convention over configuration and will

> probably generate trouble for more plugins - but I can't convince the 
> users that it's the proper way of doing it.
>
>
> directory containing:
>
> JEEFrameworkRefAppWAR
> JEEFrameworkRefAppJAVA
> JEEFrameworkRefAppEJB
> JEEFrameworkRefAppEAR
> JEEFrameworkRefApp <-- this is actually the top-pom with the modules 
> as specified above.
>
>
> so I cd into JEEFrameworkRefApp and do a
>
> mvn release:prepare -Dusername=myId -Dpassword=myScmPw
>
> and tried both with and without:
> -Dmaven.scm.provider.cvs.implementation=cvs_native
> with this flag I get:
>
> [INFO] Executing: cvs -z3 -f -q commit -R -F 
> /tmp/scm-commit-message62844.txt pom.xml AVA/pom.xml JB/pom.xml 
> AR/pom.xml AR/pom.xml [INFO] Working directory:
> /home/karltdav/work/JEEFramework/JEE/JEEFrameworkRefApp
> [INFO]
> --
> --
> [ERROR] BUILD FAILURE
> [INFO]
> --
> --
> [INFO] Unable to commit files
> Provider message:
> The cvs command failed.
> Command output:
> cvs [commit aborted]: no such directory `AVA'
>
> [INFO]
> --
> --
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Unable to commit files 
> Provider message:
> The cvs command failed.
> Command output:
> cvs [commit aborted]: no such directory `AVA'
>
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:697)
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.java:551)
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:521)
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:369)
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:266)
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:181)
>at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
>at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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.MojoFailureException: Unable to 
> commit files P

Compilation

2003-12-17 Thread Clowes, Stan, Technology VM
Hi,

can Maven compile against source as well as classes or jars?

Regards
Stan

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



Dependencies - naming,format of etc

2003-12-17 Thread Clowes, Stan, Technology VM
Hi,

New to maven and looking to use within our project. However I have some questions 
about dependencies:

The format of the location of a dependency seems very rigid i.e. :

${repo}/${groupId}/${type}s/${artifactId}-${version}.${type} 

Yes the variables can change but not the format.

Can this be altered to a directory location somewhere.

The only way I can get round this is using build or project properties which are not 
inheritable.

Also if your class file is dependent on another file in your project or another 
project for compilation i.e. the other file is not in a jar file; how do you resolve 
that dependency a none jar based dependency.

Regards
Stan

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