ad your point 2)
For what i've experienced, the dependencies of a WAR
may only be derived if the actual project itself is of
type WAR too.
As opposite, the dependencies from a WAR imho must not
be derived if the actual project is e.g. of type EAR.
Do we need any further distinction?
lg,
strub
On 11/14/06, Brett Porter <[EMAIL PROTECTED]> wrote:
If you are just looking for 2.0.5, you need to check out /branches/
maven-2.0.x instead of /trunk from under components.
It seems the instructions need to be revised for trunk (it should be
maven-cli, not maven-core there) - would you mind fi
Hi,
If you are just looking for 2.0.5, you need to check out /branches/
maven-2.0.x instead of /trunk from under components.
It seems the instructions need to be revised for trunk (it should be
maven-cli, not maven-core there) - would you mind filing a bug for that?
Thanks,
- Brett
On 15/
Wendy:
This is funny you recommended AppFuse. I just became one of the developers
there today and I've been in discussion with Matt Raible tonight about just
using the archetype to start the AppFuse structure and then bringing in the
dependent pieces by configuring your POM afterward.
Thanks fo
I'm building mvn 2.0.5 for the fix:
http://jira.codehaus.org/browse/MNG-1908
I'm following the instructions at
http://maven.apache.org/guides/development/guide-building-m2.html
On the final stage of building the binary distribution:
cd maven-core
mvn assembly:assembly
I'm getting an error:
[
On 11/14/06, David Whitehurst <[EMAIL PROTECTED]> wrote:
I'm creating an archetype for a rather large web application architecture.
This architecture contains various technologies. It would be very useful if
e.g. one archetype could be created and after the archetype:create command
was issued,
Mark Hobson wrote:
On 05/11/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>> maven-dependency-plugin: John Tolentino or Brian Fox
Brian Fox is taking care of this one. John is working on the WAR plugin.
>> maven-surefire-plugin: Kenney
>> maven-pmd-plugin: Joakim
>> maven-checkstyle-plugin: Joa
Yes, it can, as it uses some code from PropertyUtil. The code may be a bit
ugly though, as the latest version of Maven Embedder (2.0.4) doesn't seem to
work properly with the code.
Stephane Nicoll-2 wrote:
>
> Hi,
>
> I think this can include the resources filtering we need in various
> mojos
Graham Leggett wrote:
Dennis Lundberg wrote:
There has not been any official release of the site-plugin yet, that
incorporates this fix.
You can build the plugin yourself from source, by downloading it from
SVN. Then you just run "mvn install". You alse need to bump the
version number for t
Hi Graham,
No soon. The current site plugin needs Maven 2.1 and not 2.0.x.
The next release of Maven is 2.0.6, attempted for the end of the year.
Cheers,
Vincent
2006/11/14, Graham Leggett <[EMAIL PROTECTED]>:
Dennis Lundberg wrote:
> There has not been any official release of the site-plug
Dennis Lundberg wrote:
There has not been any official release of the site-plugin yet, that
incorporates this fix.
You can build the plugin yourself from source, by downloading it from
SVN. Then you just run "mvn install". You alse need to bump the version
number for the site-plugin in your
Graham Leggett wrote:
Dennis Lundberg wrote:
MSITE-91 was closed by me after committing r473599 [1] which hopefully
solves the issue. Please try it and see if it works for you.
[1] http://svn.apache.org/viewvc?view=rev&revision=473599
MSITE-91 claimed a fixed version of "2.0" which has not
Dennis Lundberg wrote:
MSITE-91 was closed by me after committing r473599 [1] which hopefully
solves the issue. Please try it and see if it works for you.
[1] http://svn.apache.org/viewvc?view=rev&revision=473599
MSITE-91 claimed a fixed version of "2.0" which has not (to my
understanding)
Hi,
I'm currently creating an howto about
installing a Maven Project Server;
The early drafts of the howto is located on
http://docs.codehaus.org/display/MAVENUSER/MavenProjectServer
Many thanks for sending me your comments.
Regards,
Raphaël
-
Hello
MSITE-91 was closed by me after committing r473599 [1] which hopefully
solves the issue. Please try it and see if it works for you.
[1] http://svn.apache.org/viewvc?view=rev&revision=473599
--
Dennis Lundberg
Franz Allan Valencia See wrote:
Good day to you, Graham,
As of the current
Just some thoughts on enhancements:
It'd be nice if we could 1) get this into the war plugin and 2) add 3
different modes:
1. Default - the way things are now, where dependencies aren't
inherited. This would allow backwards compatibility and not suprise
anyone.
2. Include Dependencies - exclud
Dependency plugin is soon. I cleaned up all the licensing issues last
night and the site is up to date. I have a few more tests I want to
write and then it's ready.
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 8:27 AM
To: Maven Developer
Sorry, my mistake. It's 2.0-alpha-1-SNAPSHOT:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/pl
ugins/maven-dependency-plugin/2.0-alpha-1-SNAPSHOT/
-Original Message-
From: asankha [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 10:49 AM
To: dev@maven.ap
I'm creating an archetype for a rather large web application architecture.
This architecture contains various technologies. It would be very useful if
e.g. one archetype could be created and after the archetype:create command
was issued, the user could be prompted to provide a selection.
Is this
Even when I specify the exact as
org.apache.maven.plugins
maven-dependency-plugin
2.0-alpha1-SNAPSHOT
I get the following:
[INFO]
[ERROR] BUILD ERROR
[INFO]
--
On Monday November 13 2006 10:47 pm, Brett Porter wrote:
> On 14/11/2006, at 2:41 PM, Daniel Kulp wrote:
> > That's an "OK" temporary solution. The biggest problem with it is
> > that
> > you cannot generate a working eclipse project with that setup. "mvn
> > eclipse:eclipe" doesn't generate a
Brian E. Fox wrote:
>
> The current version is functional; ...
I cant seem to locate this 'version' in the maven repos.. could someone
point me to where I can download this 'current' version?
--
View this message in context:
http://www.nabble.com/When-will-the-maven-dependency-plugin-be-funct
It's deployed as 2.0-alpha1-SNAPSHOT, but you'll need to add the maven
snapshots repository:
maven-snaps
http://people.apache.org/repo/m2-snapshot-repository
true
false
-Original Message-
From: asankha [mailto:[EMAIL PROTECTED]
Sent:
On Monday November 13 2006 10:55 pm, Brian E. Fox wrote:
> Hrm. I just updated the headers with outdated info. This page:
> http://www.apache.org/dev/apply-license.html should be updated to point
> to the new src-headers info.
Well, it wouldn't be apache if there wasn't at least 3 conflicting sour
Hi Minto,
Not mandatory but appreciated :)
Thanks!
Vincent
2006/11/13, Minto van der Sluis <[EMAIL PROTECTED]>:
thx, for your reply :-)
If I supply a patch, should it be for head?
Regards,
minto
Vincent Siveton wrote:
>
> [sorry for the delay]
>
> Hi Minto,
>
> mm it seems a bug.
> Fee
On 05/11/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>> maven-dependency-plugin: John Tolentino or Brian Fox
Brian Fox is taking care of this one. John is working on the WAR plugin.
>> maven-surefire-plugin: Kenney
>> maven-pmd-plugin: Joakim
>> maven-checkstyle-plugin: Joakim
>> maven-release
Brian
I am still having problems... even if I do a -U the output I get is
.
[INFO]
[INFO] The plugin 'org.apache.maven.plugins:maven-dependency-plugin' does
not exist or no valid vers
ion could be found
[INFO]
-
Got no reply to solve this issue :
On maven2 public repository, maven (m1) plugins are packaged with
".plugin" extension :
-> http://repo1.maven.org/maven2/maven/maven-changelog-plugin/1.9.1
This was not the case some weeks ago.
Maven-on-plugin creates .jar.
This sounds like a repo-converter
Hi,
I think this can include the resources filtering we need in various
mojos, right?
WDYT?
Stéphane
On 11/14/06, Tony Truong <[EMAIL PROTECTED]> wrote:
Hi guys,
For your interest, I have made a library which we have found useful here
down in Atlassian.
http://repository.atlassian.com/maven
29 matches
Mail list logo