-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Fox wrote:
>> Therefore I think that
>> the in Super-Pom caused some
>> trouble and confusion that you might not be aware of.
>
> It should use the version even if you invoke directly from the command
> line, if not, that's a separate bug.
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
> First question, wouldn't ${project.version} solve the use case of
> updating same versioned dependencies?
Nope. It would help in some of my business projects where
all artifacts get the same version when released, but
I already have a sim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
could someone have a look at
https://jira.codehaus.org/browse/MOJO-1368
If I am right, this should be moved to MSITE.
This bug is what we all see since years.
If someone was so kind to explain how to solve this,
it would be nice if this cou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brett,
Thanks for taking care. I already thought that this will gonna be ignored.
> So the summary is that if omitted on a dependency, the group ID and
> version should match that of the current project, and on deployment it
> needs to be populate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
>> On Fri, Jul 24, 2009 at 4:36 PM, Joerg Hohwiller wrote:
>> Hi there,
>>
>> I read the documentation of javadoc-plugin about goal aggregate.
>> Then I called
>> mvn javadoc:aggregate and maven failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I read the documentation of javadoc-plugin about goal aggregate.
Then I called
mvn javadoc:aggregate and maven failed saying that the goal aggregate does not
exist.
mvn -U javadoc:aggregate, same result.
Website wrong?
Aha... think...
mv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi,
Hello,
>
> I was looking at the jira roadmap for the site plugin, thinking about a
> release plan for 2.1. The main change so far is the upgrade to doxia
> 1.1, I think it would be a good idea to concentrate the next release on
> issues that a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody,
I updated my proposal and now think it is consistent and understandable.
However the examples traces still require some thoughts but
you should get the idea easily.
And finally here it is:
http://docs.codehaus.org/display/MAVENUSER/Eas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
> Quite impressive list. So there seems to be a high demand in this topic.
> Maybe we should bring some things together.
I wrote this proposal:
http://docs.codehaus.org/display/MAVENUSER/EasyVersionMaintenance
I would really love to get so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Shane,
>
>> Something that I think would be useful is a language/platform element. Then
>> it's purely additions to the POM. If you could identify the
>> language/platform and it's version would that be enough for you?
>
>
> For this element, I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
>> E.g. with maven 2.0.x you could have a module included in your
>> toplevel pom that you also add as dependency to some plugin such
>> as checkstyle or findbugs. In maven 2.1 you have to remove the
>> module declaration or you will get a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ralph,
>>
>> Okay. So thats what I guessed when I said that the MavenProject/Model is
>> just a stupid POJO and various plugins manipulate it with side effects.
>> Sounds a little hacky to me but thats the way it is. So my serialization
>> idea is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
>>
>> Do you need simple IT-projects that I shall attach to MNG-4161 and related?
>>
>
> Sample ITs for sure, and some level of detail in a proposal like these:
> http://docs.codehaus.org/display/MAVENUSER/User+Proposals
>
here is my propo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
>> Your better bet will be to try and get this documented so it can be
>> implemented in 3.x.
no change to see some improvement about version maintenance in 2.x?
See the list of issues I just posted and also look at the votes.
Thanks
Jö
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
> Your better bet will be to try and get this documented so it can be
> implemented in 3.x.
I would surely NOT mind. What do you expect?
A new xdoc? Or a diff to the actual source of
http://maven.apache.org/guides/introduction/introduction-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
After I got lost in the thread "Progress on support for large projects"
and opened MNG-4161, I started to collect everything that is going on
in JIRA about this. I added this to MNG-4161 but also wanted to
point this out here:
* MNG-624
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> I think you are referring to one of the other patches that was
> submitted, not what I committed to the MNG-624 branch.
MNG-624 or maven-2.1.x-MNG-624 ?
>>
>>
>> A big problem could be the encoding issue if you store XML in a string
>> and the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Off topic.
>
> Actually I believe this isn't true anymore.
>
> See http://jira.codehaus.org/browse/MECLIPSE-344
> "all dependent artefacts that are available in your eclipse-workspace
> will be attached as project references even if they are not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stephen,
>
> If A(1.0) has root(1.2-SNAPSHOT) as a parent it should never have been
> released as the pom for A(1.0) is based on content from root(1.2-SNAPSHOT)
> which is subject to change... which means that a released pom does not have
> a defi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> By inheriting the version, groupId, etc. from the parent - yes. The
> release plugin still handles the pom transformations and the tagging
> (SCM URLs, snapshot to release version, release to next snapshot
> version, etc.)
But there is nothing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
>>
>> OK. So you would NOT mind if maven adds some new features that
>> are compatible to older versions of maven.
>> Thats all I am fighting for.
>>
>
> No fighting required, just make a patch. If it's truly backwards compatible,
> then th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Christian,
>
> My question may have sounded rhetorically but I really meant that. You
> could of course manage commit rights with subversion so that whenever
> someone mistakenly would try to commit to that release version on trunk,
> subversion c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chistian,
>
> What stops a developer from making changes to A(1.0) on trunk,
> rebuilding locally - that is - overwriting release artifacts with
> something different in the local repository, and then later on even
> commit those changes forgettin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ralph,
>
> I've been "promised" by Jason that the work on Maven 3 is going to fix
> some of these issues. I simply haven't had the time to look at the work
> on Maven 3 and even if I had, it has been changing at a fairly rapid
> pace for months.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Milos,
>
>> mvn eclipse:eclipse does perform a build (partially) and might even produce
>> 1 eclipse project for multiple maven projects (correct me if I'm wrong)
No it does not. But I hope it will one finest day.
And it will definitely do NOT co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
> [cut.]
>
> Sorry I wasn't more specific last night at 2:00 am :-). I need more scm
> context to understand. I'm assuming something like svn with
>
> +tags
> +root-1.0 (1.0)
> +A(1.0)
> \B(1.0)
> +root-1.1 (1.1)
> +A(1.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
>> As I already said, I talked about release-plugin and my view of the world
>> and it seems NOT to fit together. My POM-tree follows strict logical
>> aspects that is motivated by the architecture of the project and NOT by
>> the philosophy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
> I did not yet get the point, why you have to write a new pom.xml to the disc.
> My naive illusion was that there is a central component that reads and parses
> the POM in maven where you can hook into and perform the transformation.
> Then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Fox wrote:
>>
>>> Can you give more details about what doesn't work or doesn't match your
>>> process?
>> E.g. it tried to convince me to release all modules of my entire project
>> and complained if some module had a non SNAPSHOT version.
>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ralph,
>>> Hi there,
>>>
>>> absolutely everybody having large maven projects is
>>> annoyed by maintaining the versions in all the poms.
>>>
>>
>> Are you using the release plugin?
>
> This problem probably goes away for anyone able to use the re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Milos,
>
> relying on the reactor and giving up on being able to build the one project
> separately is very bad (read: completely breaks) any IDE integration.
I totally disagree. I am successfully using maven-eclipse-plugin (mvn
eclipse:eclipse) a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
>>> Are you using the release plugin?
>> Nope! I tried it and came to the point that is no good for me.
>> I also had a discussion with the developers long time ago
>> and filed some feature request. Anyhow I still think this
>> is the wrong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Hi there,
thanks for your answer...
>>
>> absolutely everybody having large maven projects is
>> annoyed by maintaining the versions in all the poms.
>>
>>
> Are you using the release plugin?
Nope! I tried it and came to the point that is no g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
absolutely everybody having large maven projects is
annoyed by maintaining the versions in all the poms.
Additionally the complete solution is quite simple
and seems to be quite common sense:
1. Allow to omitt versions in as well
as in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I found that there is a little list of incompatibilities form m2.1 at:
http://maven.apache.org/release-notes.html
However there are a lot more.
E.g. with maven 2.0.x you could have a module included in your
toplevel pom that you also add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
> >
> > so far so good.
> > I have the following suggestions:
> >
> > 1. Also specify that the pom.filters are
> > in the order of their declaration in
> > the XML.
> They are not used (as they are not used in resources plugin 2.2 and
> addi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
>> The additions Dain has made to XBean adds things I was just never
>> interested in like constructor injection and bean factories.
>
> Also xbean-reflect "thinks" in java.lang.reflect.Type terms so it's easy
> to add converters that are g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi,
Hi there,
as often I a little late on some threads ;)
> I have start a proposal [1]
so far so good.
I have the following suggestions:
1. Also specify that the pom.filters are in the order of their declaration in
the XML.
2. Resolve variable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
| In POM we have a version number of the project as
|
| 1.4
|
| Instead of hardcoding it each time I take a new build, I would like to
| replace it with the one entered by the user when he takes a buld using
| maven. I want the user to enter the v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
just to give my feedback on the thread:
+1 for NOT overloading 2.1
When it is about further versions and long term future of maven:
- -infinity for
artifact="org.apache.maven:maven-project:2.0.8"
How do you want to express versions range
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
it seems I get ignored with this toppic on all channels.
I will try to create a JIRA issue, maybe that gets read one day...
Regards
Jörg
> Hello everybody,
>
> I posted to the users list but got no answer.
> Further I think of a deeper integr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I wrote:
> I would prefer that if maven builds a plugin that has no goal "help" already,
> then it auto-generates one in about the same way as it does
> when generating the goal-documentation for the site. Then each plugin
> would have (in f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
>>> Finding the definitive help information for a plugin should be
>>> absolutely trivial and built-in; having the CLI option which give the
>>> code-you-are-executing-right-now the ability to answer that question
>>> avoids the issues we have toda
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody,
I posted to the users list but got no answer.
Further I think of a deeper integration now
so dev-list might make more sense...
| Hi there,
|
| I just wonder if there is already a plugin for maven2
| that can generate a table with th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
| Right...I guess it'd help to include the URL:
|
| http://docs.codehaus.org/display/MAVEN/Deterministic+Lifecycle+Planning
|
| Thanks!
I generally agree with what you are saying.
You are pointing out common problems very well.
The solution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
| Heh, so you are willing to trade "build reproducibility" (for all
| projects linked to central repo) for "care about the community"? o.O
|
| Hrm, please put that on a vote before you do it!
|
| IF you are talking about putting up "dummy"
ea under MNG-3381
| (http://jira.codehaus.org/browse/MNG-3381) and will put it on my agenda
| to revisit it next time I come back to error reporting.
|
| Thanks,
|
| -john
|
| On Jan 25, 2008, at 6:52 PM, Joerg Hohwiller wrote:
|
| Hi there,
|
| typically if maven fails with something like "req
k or white
You are right. But again I just want to say be as sensible about changes as
possible. Therefore my oppinion is: yes add these poms but without dependencies.
If dependencies should be added, new versions have to be created.
Take care
~ Jörg
|
|
| On Jan 25, 2008 4:16 PM, Joerg Hohwill
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I am sometimes late on threads but anyways...
| i don't agree, the point of not having a pom there is to be able to
| add one later with the right info. If you work against something
| without pom, hey, it's your decision, but you are awar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
typically if maven fails with something like "required artifact is missing"
you can have a look at the module where the error occurred and scan
the dependencies.
As additional support maven typically prompts an error report including
someth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I noticed that maven.test.skip is just a convenience property specially
interpreted by plugins like surefire.
Besides I could NOT find a way to skip integration-tests when tests are
configured to run in that phase instead. This causes the bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
> The biggest problem as I see it is not the groupId structures (although it
> DOES bother me...) but rather the dependencies metadata which is often
> incorrect, or atleast not quite right. Examples are numerous and range from
> optional dep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi,
Hello,
>
> I'd like to throw in my 2 cents. The maven repository was (as I recall)
> started back in the Maven 1.x days, when people didn't REALLY do ANY
> dependency management. Since then, the repository grew, Maven1.x grew and
> grew. A while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I am seeing more and more the need that the community takes better control over
what is dumped into the central repo. This seems to get more and more like a
rubbish dump. There are duplications of the logically same artifacts. This
causes ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
while just submitting a bug to maven-dependency-plugin for NOT working when to
include or exclude multiple groupIds (MDEP-87) I thought about it and ask
myself:
Why isn't this implemented in the maven core itself? Then all plugins could
ben
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
> On 4/12/07, Aaron Digulla <[EMAIL PROTECTED]> wrote:
>>
>> Joerg Hohwiller wrote:
>> > Hi there,
>> >
>> > I have already used SWT and GWT together with maven. Both need native
>> sys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marc,
> We can change the license to something else, no problem.
Of course this is your decision.
But you could think about dual licensing your project.
Here is something to consider:
http://wiki.apache.org/jakarta/Using_LGPL'd_code
>
> Regards
> M
would like to
understand. Maybe there is something I am missing that would help me
to live better with the inconvenience or prevent me from adjusting this in my
toplevel POM.
Thanks
Jörg
>
>
> Joerg Hohwiller wrote:
> Hi there everybody,
>
> from the separation of concerns vie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi
Hello Mark,
>
> the freehep-nar-plugin does exactly what you describe.
>
> http://java.freehep.org/freehep-nar-plugin
Thanks for the hint. This sounds promising.
Anyways I am not creating system libraries, I just want to use them in my
project.
rg
>
> On 4/6/07, Joerg Hohwiller <[EMAIL PROTECTED]> wrote:
>>
> Hi there,
>
> I have already used SWT and GWT together with maven. Both need native
> system
> libraries at some specific point. This causes trouble when running code (
> e.g.
> test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I have already used SWT and GWT together with maven. Both need native system
libraries at some specific point. This causes trouble when running code (e.g.
test-cases) with maven.
Are there any plans to add dependencies with dll (or
so) to j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joerg Hohwiller schrieb:
> Hi there,
Hi again,
for those who dig in the archives and hit this thread:
The problem has been solved. Fixes for JXR and cobertura are not yet released
but this is just a matter of time. For JXR a fixed version is alre
> Hi Joerg,
Hi Vincent,
>
> 2007/2/15, Joerg Hohwiller <[EMAIL PROTECTED]>:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> Hi everybody,
> >
> > I am figthing with site:stage and am quite desperate now :(
> >
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody,
I am figthing with site:stage and am quite desperate now :(
Could you please help me with MCOBERTURA-63?
http://jira.codehaus.org/browse/MCOBERTURA-63
I am totaly clueless and actually I want to USE maven instead of DEVELOPING
maven. B
Hi there,
> Here's the issue I discovered with 2.0.4 and JDK 6. AppFuse 2.x users have
> reported other issues (i.e. plugins not firing) when using JDK 6.
>
> http://jira.codehaus.org/browse/MNG-2709
>
> Matt
FYI: I am using maven2 with JDK6 and had no problems so far.
I am using junit4 and I on
nt
> http://jira.codehaus.org/browse/MNG
>
> Cheers,
>
> Vincent
>
> 2006/8/29, Joerg Hohwiller <[EMAIL PROTECTED]>:
> Hi there,
>
> as I promised some time ago, I wanted to provide my work in creating a
> maven2
> plugin for solaris packaging. I uses an ant mojo an
Hi there,
>> I had no specific objections once the 2.1-SNAPSHOT dependency was
>> removed.
>>
>> There are 2 open issues for the current version, though, and I'm a bit
>> concerned at releasing it as "final" when there are 64 other issues
>> open. Should it still be beta?
+1
>
> I just want to ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there everybody,
from the separation of concerns view of the maven plugins I can see the point in
separating "java" and "resources" in src/main and src/test.
- From the users point of view this is quite ugly:
- -If you are looking at a java file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jason,
[cut]
>> thanks for your work. I tried to build my site with maven 2.0.4. and
>> maven-site-plugin 2.0-SNAPSHOT and now javadoc seems to work even if
>> the site is staged (site:stage). I do not know if that was intended by your
>> fix.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason van Zyl wrote:
> Hi,
Hi Jason,
thanks for your work. I tried to build my site with maven 2.0.4. and
maven-site-plugin 2.0-SNAPSHOT and now javadoc seems to work even if
the site is staged (site:stage). I do not know if that was intended by your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
since may 2006 the following issue is blocking the site gerneration of serious
projects:
http://jira.codehaus.org/browse/MSITE-138
This issue has been closed with the message that it has been fixed in version
2.0 of the site-plugin.
I trie
tag to do this or should I open a feature request in JIRA?
Regards
Jörg
- Original Message
Subject: toc feature in xdoc?
Date: Sun, 29 Oct 2006 21:42:31 +0100
From: Joerg Hohwiller <[EMAIL PROTECTED]>
Reply-To: Maven Users List
To: Maven Users List
Hi there,
in th
apache.org/repos/asf/maven/plugins/trunk/maven-
>> project-info-reports-plugin
>> - mvn -Papache install
>>
>> HTH
>>
>> Could you provide us the full stack trace? I dont see any reference to
>> maven-plugin-plugin:2.0-alpha-3.
>>
>> Chee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Vincent,
> Could you provide us the full stack trace? I dont see any reference to
> maven-plugin-plugin:2.0-alpha-3.
here it is...
Jörg
[EMAIL PROTECTED]:~/projects/maven-plugins/maven-plugin-plugin$ mvn -X install
+ Error stacktraces are turned o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent Siveton wrote:
> Hi Jörg,
Hi Vincent,
thanks for your quick reply...
>
> Based on your comments, here are my succesfull steps to build
> maven-site-plugin from scratch:
> - dwl and install m2-20060828.203000.tar.gz
ok
> - removed my repositor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
as I promised some time ago, I wanted to provide my work in creating a maven2
plugin for solaris packaging. I uses an ant mojo and only works on a solaris
machine with pkgtools installed.
For the moment I set in the POM
groupId to org.apach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
As fix for MSITE-138, I want to build the maven-site-plugin from trunk.
As I figured out, I also need to update maven-plugin-plugin that also requires
me to update maven itself. As suggested by Vincent, I got the latest integration
build wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
what is the actual state about javax JARs at ibiblio?
I have seen that javax.mail is available as JAR in the central repo.
Does this mean that potentially other javax JARs could be made available there?
I would love to java "javax.annotation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jan,
Jan Nielsen wrote:
> I'm a newbie to Maven and Continuum, so aplogies if this is obvious. I'm
> not sure if this is a Maven question or Continuum question, or perhaps
> both, so I thought I'd try here first.
>
> When dealing with multiple p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Graham Leggett wrote:
> Hi all,
Hi,
>
> Do transitive dependencies work within m2eclipse v0.0.9?
They do work for me. I have quite a lot of projects with many dependencies.
> In the case
> where eclipse project A depends on eclipse project B, and e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mike,
SingleShot wrote:
> I have several cases where I need to override the default JDK implementations
> via the Java endorsed JAR override mechanism (for example, by setting
> java.endorsed.dirs). When I create a software distribution, I use the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stephen,
Stephen Duncan wrote:
> Two pieces of info: there is already an optional tag in the parent
> that allows you to specify where the parent is - :
>
> http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html#class_parent
>
>
> Als
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jörg
>
> Have a look at the "Better builds with Maven" book.
> There's an example for a mojo and for an Ant based plugin.
>
Thanks for the hint...
I am going to work this out...
Its unbelivable to have such documentation if you have been strzgge
Date: Wed, 05 Apr 2006 23:24:09 +0200
From: Joerg Hohwiller <[EMAIL PROTECTED]>
Reply-To: Maven Users List
To: users@maven.apache.org
Hi there,
I have been using maven and now m2 for quite a while. Anyways I just wanted to
let you know that I often get mails from people who get in trouble b
tory report, maven-release-plugin, etc.
Thinks that are not working properly are just "bugs".
Regards
Jörg
p.s. sorry for top-posting ;)
>
>
> Joerg Hohwiller wrote:
>
> Hi there,
>
> I have a complex maven project that goes down to 3 levels of POM
> inhe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Porter wrote:
> I think this has already been suggested in JIRA, but if not it is worth
> adding.
I only found issues that are slightly related, but not yet the same thing.
I'll put it into JIRA on monday...
>
> - Brett
Thanks
Jörg
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörg Schaible wrote:
> Hi Jörg,
Hi Jörg,
nice to "meet" again ;)
>
> [snip]
>
> So did you have multiple modules for each Solaris package or a single module
> with a Mojo that creates two artifacts (like the EJB and its client)?
I created one modul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I have a complex maven project that goes down to 3 levels of POM inheritance (=
it has sub-sub-projects).
I am not really sure about what the suggested layout is:
TREE:
trunk/
trunk/foo-project/pom.xml
trunk/foo-project/foo-project-util/p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Maven2 really rocks! I figured out a way to build a plugin that allows
"solaris" as and builds a solaris package for a maven project.
Therefore I add the complete "static" content of the package to the
main/resources. Further I have a filt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I read about the Super-POM at:
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
My question is now, if it was possible to add an additional resources directory
that is filtered. It would not hurt anybody if he does n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
first of all I have to say that the dependency-management of maven2 is really
cool! The scope is covering all needs I can think of and the transitive
dependency thing is really nice...
Anyways here are some ideas about the dependency manage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
currently I can not access www.ibiblio.org while sf.net, codehause.org, etc. is
accessable without problems. Is there a temporary downtime?
Thanks
Jörg
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Joerg Hohwiller wrote:
> Hello Brett,
>
> Brett Porter wrote:
>
>>>We've so far opted not to do this (basically an optional dependency) as
>>>it can encourage poorly specified poms to stay that way.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trygve Laugstøl wrote:
> On Wed, Aug 10, 2005 at 08:26:16PM +0200, Joerg Hohwiller wrote:
>
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>Hi Trygve,
>>
>>
>>>>So I need a toplevel PO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Trygve,
>>So I need a toplevel POM that is NOT "broken".
>
>
> You need to use the latest Maven 2 from trunk to be able to build Maven 2.
> Read up on how to build Maven 2 here[1].
>
> [1]: http://maven.apache.org/maven2/building.html
>
>
I DO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trygve Laugstøl wrote:
> On Wed, Aug 10, 2005 at 06:49:40PM +0200, Joerg Hohwiller wrote:
>
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>Hi there,
>>
>>I got a little lost in jakarta-commons
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I got a little lost in jakarta-commons since my "getting involved?"
thread, but finally I checked out the complete m2 thing.
You tailered your components quite small - which (usually) leads to a
gread design. Anyways I am little frustrated s
and choose the implementation by another dependency.
So all I am saying is: you're right and maven(2) enforces structuring
your projects, which is good :)
>
> - Brett
>
> Joerg Hohwiller wrote:
>
>
>>Hi there,
>>
>>John Casey wrote:
>>
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
John Casey wrote:
> try adding true to the plugin definition at the top
> level...I can't remember whether the compiler plugin inherits by default
> or not (my suspicions are "not").
Not about POM inheritance but about dependency inheritanc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Thomas,
Thomas Van de Velde wrote:
>>BTW - I like plexus. Haven't noticed the project before. I had used
>>avalon and had a look at pico+nano before. Plexus seems to be powerfull
>>like avalon containers but less invasive (like the spring-framework
100 matches
Mail list logo
