Re: How to use wagon-ssh-external instead of wagon-ssh?

[Brett Porter]

On 02/05/2011, at 8:11 PM, Andreas Sewe wrote:

> Hi Brett,
> 
>> I think in the Maven 3 version of the site plugin, you need to add
>> the wagon as a dependency of the site plugin, instead of as an
>> extension (which only applies to the core deployment components).
> 
> thanks for your suggestion. I am afraid, it didn't help: When declaring a 
> plugin dependency, the maven-site-plugin now has both 
> org.apache.maven.wagon:wagon-ssh-external:jar:1.0-beta-7 and 
> org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-6 as a dependency, but it still 
> insists on using the latter for sftp URIs. :-(
> 
> Any other suggestions?
> 

Apologies for not noticing that detail sooner. The external wagon doesn't have 
a handler for sftp - only scpexe.

- Brett


--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter





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

Plugin to retrieve parents as dependencies....

[Lindsay Smith]

The dependency goal 'dependency:tree' goal works great for finding 
dependencies, but it doesn't list the parent of your pom itself.So if my 
project inherits from project 'parent.project', and I run dependency:tree, then 
my dependencies, and those of 'parent.project', are listed, but 
'parent.project' is not.

Is there any way to get the parent pom (and its parent(s) if it has them) 
reported from a plugin?

Lindsay

Re: reordering the lifecycle

[Justin Lee]

That's what I ended up.  Thanks to whomever initially suggested that.  I'm
not even sure I knew that phase existed before that.

On Mon, May 2, 2011 at 7:51 PM, Benson Margulies wrote:

> Bind surefire to the integration-test phase, that runs post-packaging.
>
> On Fri, Apr 29, 2011 at 3:05 AM, Ron Wheeler
>  wrote:
> > On 28/04/2011 5:35 PM, Justin Lee wrote:
> >>
> >> I have a huge tree of ant based projects i'm trying to convert to maven.
> >>  I
> >> have the mechanics worked about except for a minor hitch:  I need the
> test
> >> phase to be the last one executed.  Since all of this code is test code
> >> there will be no artifacts to install, no deployments run.  But I need
> to,
> >> say, generate the war files before surefire kicks off and runs the test.
> >>  How can I do that?  Could I bind the surefire plugin to the install
> phase
> >> instead?
> >>
> > Try to identify the "Maven way" to do what you are doing.
> > Maven is not Ant.
> >
> > Don't be tempted to invent something new unless you are sure that no one
> > else has ever tried to develop an application like yours.
> > There is a Maven Best Practice for almost every situation and most likely
> > thousands of people have already set up a project like yours. It
> somethings
> > takes a bit of digging to find out the "right" way.
> >
> >
> > Ron
> >
> > -
> > 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: reordering the lifecycle

[Benson Margulies]

Bind surefire to the integration-test phase, that runs post-packaging.

On Fri, Apr 29, 2011 at 3:05 AM, Ron Wheeler
 wrote:
> On 28/04/2011 5:35 PM, Justin Lee wrote:
>>
>> I have a huge tree of ant based projects i'm trying to convert to maven.
>>  I
>> have the mechanics worked about except for a minor hitch:  I need the test
>> phase to be the last one executed.  Since all of this code is test code
>> there will be no artifacts to install, no deployments run.  But I need to,
>> say, generate the war files before surefire kicks off and runs the test.
>>  How can I do that?  Could I bind the surefire plugin to the install phase
>> instead?
>>
> Try to identify the "Maven way" to do what you are doing.
> Maven is not Ant.
>
> Don't be tempted to invent something new unless you are sure that no one
> else has ever tried to develop an application like yours.
> There is a Maven Best Practice for almost every situation and most likely
> thousands of people have already set up a project like yours. It somethings
> takes a bit of digging to find out the "right" way.
>
>
> Ron
>
> -
> 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: reordering the lifecycle

[Justin Lee]

I understand and fully support The Maven Way.  But this is a tree of 500+
tests in this tree alone (there's at least another half dozen other trees)
I'm trying to script the conversion for.  There's a limit to how much I can
script reliably.  In this case the code being tested is built elsewhere.
 This tree generates artifacts (test wars and servlets, e.g.) that are
deployed and then used in testing.  But these artifacts and tests both live
in essentially the same maven module.  Yes, it's more than mildly crappy.
 Yes, there are betters ways to do this if you're starting from scratch.
 But this test code and the "framework" it's built on are 10+ years old in
some cases and far predate maven, testng, and junit.  I'm trying to bring
this code in to the 21st century bit by bit but I can only do so much at
once.  So for now, making the default goal "integration-test" is exactly
what I needed.

On Mon, May 2, 2011 at 6:08 PM, Ed Hillmann  wrote:

> On Fri, Apr 29, 2011 at 5:05 PM, Ron Wheeler <
> rwhee...@artifact-software.com
> > wrote:
>
> > On 28/04/2011 5:35 PM, Justin Lee wrote:
> >
> >> I have a huge tree of ant based projects i'm trying to convert to maven.
> >>  I
> >> have the mechanics worked about except for a minor hitch:  I need the
> test
> >> phase to be the last one executed.  Since all of this code is test code
> >> there will be no artifacts to install, no deployments run.  But I need
> to,
> >> say, generate the war files before surefire kicks off and runs the test.
> >>  How can I do that?  Could I bind the surefire plugin to the install
> phase
> >> instead?
> >>
> >>  Try to identify the "Maven way" to do what you are doing.
> > Maven is not Ant.
> >
> > Don't be tempted to invent something new unless you are sure that no one
> > else has ever tried to develop an application like yours.
> > There is a Maven Best Practice for almost every situation and most likely
> > thousands of people have already set up a project like yours. It
> somethings
> > takes a bit of digging to find out the "right" way.
> >
> >
> > Ron
> >
>
> Another option which I've found useful is separate the tests into a
> different module from the code being tested.  This is quite
> straight-forward, and you can use Maven dependencies to ensure the tests
> are
> running against the right version of the WAR file.  So, you'd have the
> original module that builds the WAR file (and whatever appropriate
> Unit-level tests remaining in this module... any tests that don't require a
> packaged and/or deployed WAR file), and a new module which contains only
> those tests that require the WAR file.  I do this with my Selenium tests.
>
> This is a nice Maven-way of doing it, ensuring I don't run my Selenium
> tests
> if the WAR doesn't build.
>
> Just another thought. :)
>
> Thanks,
> Ed
>

Re: collecting dependent artifacts

[Eric Kolotyluk]

OK, shade is doing mostly what I want, except I cannot seem to configure 
it to include classes from a sibling module in Maven.


My structure is something like

parent/pom.xml
service-module/pom.xml
common-module/pom.xml
client-module/pom.xml

I want the service-module.jar to contain the classes from common-module, 
but can't figure out how. I tried putting the coordinates of 
common-module into my service-module/pom.xml, but Maven complains 
because it cannot find common-module in any repository.


Right now my service-module/pom.xml looks like



org.apache.maven.plugins
maven-shade-plugin
1.4


shade
package

shade




*:*
com.kodak.intersystem:intersystem-common



implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">

com.kodak.intersystem.service.Service









Eventually I also want client-module.jar to include the common classes too.

I'm I overlooking something obvious?

Cheers, Eric


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

Re: reordering the lifecycle

[Ed Hillmann]

On Fri, Apr 29, 2011 at 5:05 PM, Ron Wheeler  wrote:

> On 28/04/2011 5:35 PM, Justin Lee wrote:
>
>> I have a huge tree of ant based projects i'm trying to convert to maven.
>>  I
>> have the mechanics worked about except for a minor hitch:  I need the test
>> phase to be the last one executed.  Since all of this code is test code
>> there will be no artifacts to install, no deployments run.  But I need to,
>> say, generate the war files before surefire kicks off and runs the test.
>>  How can I do that?  Could I bind the surefire plugin to the install phase
>> instead?
>>
>>  Try to identify the "Maven way" to do what you are doing.
> Maven is not Ant.
>
> Don't be tempted to invent something new unless you are sure that no one
> else has ever tried to develop an application like yours.
> There is a Maven Best Practice for almost every situation and most likely
> thousands of people have already set up a project like yours. It somethings
> takes a bit of digging to find out the "right" way.
>
>
> Ron
>

Another option which I've found useful is separate the tests into a
different module from the code being tested.  This is quite
straight-forward, and you can use Maven dependencies to ensure the tests are
running against the right version of the WAR file.  So, you'd have the
original module that builds the WAR file (and whatever appropriate
Unit-level tests remaining in this module... any tests that don't require a
packaged and/or deployed WAR file), and a new module which contains only
those tests that require the WAR file.  I do this with my Selenium tests.

This is a nice Maven-way of doing it, ensuring I don't run my Selenium tests
if the WAR doesn't build.

Just another thought. :)

Thanks,
Ed

Surefire is very slow on old JUnit3 tests with suite() methods

[Linus Tolke Tigris]

Hello Surefire experts!

In the ArgoUML project the JUnit tests could be improved. Nevertheless we
have been running them more or less nightly for more than 6 years. They run
from ant with fork=yes and forkMode=perTest.

To modernize this I am attempting to run the same tests from a Hudson+Maven
setup instead. In the first attempt I didn't find how to make the tests run
each in its own jvm so almost half of the tests failed (901 fails out of
2014 same tests with and without coverage). Last night I finally understood
how to make Surefire fork a jvm for each test (always)
and the set the java.awt.headless and some other properties and managed to
get 439 tests to work (there is more work to be done in this area).

The problem I noticed with the setup is that running the tests as forking
per test is really slow. Because of some configuration issues, paths not set
up correctly, I noticed that the suite() methods were called for every test
case for every fork. We have a handful of tests that use the suite() method.
These does some file parsing and clever searches and that time is well spent
when running these specific tests. But for most tests, this is pointless. I
don't even see the point in loading tests that are not supposed to be run in
each fork. When I looked at how it performed each jvm consumed about 1
minute and 15 seconds of CPU while the test reported time spent of a few
seconds only. (This was on my 400MHz build host. On my 3GHz desktop machine
it takes only 45 seconds of CPU).

I get the feeling that something in the setup (Maven, Surefire, Junit 4.8.1,
old junit3 test cases) goes through all existing test cases for every fork
and run the suite() methods. The entire build took 8 hours instead of 3 that
I had expected (it took 2 hours before).

How do I turn this off? How do I get each fork to just load and run the test
case it is supposed to run?

The hudson build is at: http://closettop.homelinux.org:8080/job/maven-build/
.
The source (including poms) can be retrieved using svn from
http://argouml.tigris.org/svn/argouml/trunk or browsed at
http://argouml.tigris.org/source/browse/argouml/trunk/. The problem is in
the argouml-app subsystem.
As you can see, if you attempt mvn test, the text "Skipping 15 abstract
elements" is written once per fork from within suite() in the
org.argouml.model.TestAgainstUmlModel class.

/Linus

uisng maven ant task behind proxy

[rjilani]

Gurus I am trying to use the maven ant task behind the proxy but couldn't
make it work. I am bit confuse that what if we already have a proxy setting
in ./conf/settings.xml, will it work or not. In my case it is not working. I
have looked into the maven ant task documentation
(http://maven.apache.org/ant-tasks/reference.html#remoteRepository) but
couldn't detect how to make it work. Do we have to override it in the ant
task if yes, is there any example of doing it. 

Besides this I have couple of other questions

1. Can we have more then 1 remote repository in ant build file e.g 

http://download.java.net/maven/2/";>


http://repository.jboss.com/maven2";>


2. in the case above do I still have the default repository 
http://repo1.maven.org/maven2";>
 or the default will be override by the above 2
repositories

Thanks,
RJ.

--
View this message in context: 
http://maven.40175.n5.nabble.com/uisng-maven-ant-task-behind-proxy-tp4365527p4365527.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

Re: Maven release plugin question

[Karl Heinz Marbaise]

Hi, you should the configuration for the maven-release-plugin

autoversionsubmodules which can be done either on command as well in the 
pom.


In this situation i would suggest to configure the maven-release-plugin 
in the parent pomwith it's appropriate configuration...


Furthermore you should prevent using of ${parent.version} in your 
reactor pom neither in you modules pom's...you should define the version 
only via at the parent pom..
I would suggest also to define the groupId of the project only once in 
the parent pom ...


Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen   http://www.soebes.de

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

Re: Need help with m2eclipse 0.13 + war:exploded

[Wayne Fay]

> I'm using m2eclipse 0.13 from the /N/ update site, trying to achieve
> one of the "holy grails" of integration: Google App Engine + Scala [+
> Lift, optionally] + Eclipse with m2e. Solving this problem would be a

M2E questions below on the M2E lists:
http://m2eclipse.sonatype.org/project-information.html

Wayne

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

Re: Need help with m2eclipse 0.13 + war:exploded

[Todd Vierling]

On Mon, May 2, 2011 at 2:17 PM, Todd Vierling  wrote:
> I'm using m2eclipse 0.13 from the /N/ update site, trying to achieve
> one of the "holy grails" of integration: Google App Engine + Scala [+
> Lift, optionally] + Eclipse with m2e. Solving this problem would be a
> win for a whole lot of developers out there (and it might also make
> more "vanilla" WAR packaging easier to describe, too).

I should really have said that even Scala isn't at issue here.
Basically, it's GAE with Google Plugin for Eclipse + Eclipse with m2e
+ getting dependencies into place. Once the dependencies properly get
into war/, it really applies to any GAE project inside Eclipse using
any JVM language.

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

Need help with m2eclipse 0.13 + war:exploded

[Todd Vierling]

I'm using m2eclipse 0.13 from the /N/ update site, trying to achieve
one of the "holy grails" of integration: Google App Engine + Scala [+
Lift, optionally] + Eclipse with m2e. Solving this problem would be a
win for a whole lot of developers out there (and it might also make
more "vanilla" WAR packaging easier to describe, too).

Environment: Eclipse 3.6.2, Google Plugin for Eclipse 2.3.0beta1,
Scala IDE Plugin "wip-backport" nightly with 2.8.1 runtime, m2e 0.13
nightly as noted above.

I have all the necessary dependencies in the POM, including a
dependency on a sibling project, and compiling is just fine. To get
this to package up, I know I need a war:exploded layout (since GAE's
deployment will do its own archiving of /war).

However, I don't know what to do to get the dependencies (the JAR
dependencies from the project's POM and the plain classes from the
sibling project) into war/. I note that the copy-dependencies goal is
explicitly disallowed with an error in m2e 0.13, so I'm not sure what
is now responsible for getting the dependencies into the WAR. Further,
I don't know how to tell Eclipse to make Maven actually do that at
some point before I deploy (since the Maven Builder is no longer
configurable at all in 0.13).

POM follows. Whether this is a plain Scala or Lift project doesn't
really matter; the dependency chain is the only real difference.

http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.duh
duh-lifttest
war
0.0.1-SNAPSHOT



UTF-8





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

1.6
1.6



org.apache.maven
maven-war-plugin
2.1.1

exploded



war/WEB-INF/classes




net.liftweb
lift-mapper_2.8.1
2.3


org.slf4j
slf4j-jdk14
1.6.1


org.duh
duh-util
0.0.2-SNAPSHOT




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

Maven release plugin question

[Yaakov Chaikin]

Hi all,

I've used the maven release plugin for a long time, but I have always
used it in situations when the room POM was the parent POM at the same
time.

Now, I am a project where that's not an option, but they still want to
use the maven release plugin. Instead, their structure is as follows:

pom.xml --- reactor pom (listing modules)
 -- bla-parent (pom.xml lists plugins, dependencies,etc.)
 -- bla-model (regular pom.xml)
 -- bla-ddl (regular pom.xml)

You get the point.

Here is the reactor's pom.xml:
***
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>

4.0.0
bla
bla-reactor
pom
Bla Reactor
${parent.version}


bla
bla-parent
1.0-SNAPSHOT
bla-parent



bla-ddl
bla-common
bla-model
bla-persistence
bla-web



***

Here is how moduleOne's pom.xml looks like:
***
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>

4.0.0
bla
bla-model
jar
Bla Model
${parent.version}


bla
bla-parent
1.0-SNAPSHOT
../bla-parent

***

When I run 'mvn release:prepare' from the root directory (the one that
hosts the reactor POM), I end up with this:
*
...
...
[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3)
1: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3)
1: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3)
1: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3)
1: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3)
1: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
There are still some remaining snapshot dependencies.
: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3)
1: : 1
Dependency 'bla:bla-parent' is a snapshot (1.0-SNAPSHOT)
: Which release version should it be set to? 1.0: :
What version should the dependency be reset to for development? 1.0: :
What is the release version for "Bla Reactor"? (bla:bla-reactor) 1.0: :
What is SCM release tag or label for "Bla Reactor"? (bla:bla-reactor)
bla-reactor-1.0: :
What is the new development version for "Bla Reactor"?
(bla:bla-reactor) 1.1-SNAPSHOT: :
[INFO] Transforming 'Bla Database scripts'...
[INFO] Transforming 'Bla Common'...
[INFO] Transforming 'Bla Model'...
[INFO] Transforming 'Bla Persistence'...
[INFO] Updating bla-common to 1.0
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 

Re: collecting dependent artifacts

[Wayne Fay]

> If you want to write an installer for foo.jar, how do you collect all the
> dependencies like bar.jar together to distribute with your application
> installer?

maven-shade-plugin
assembly plugin
appassembler
etc

> In a similar fashion, when you do a release, don't you want to check all
> your dependent artifacts like bar.jar into source control so you can rebuild
> that release again without worrying that that version of bar.jar has
> vanished from all repositories on earth?

Nexus
Archiva
Artifactory
etc

Wayne

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

collecting dependent artifacts

[Eric Kolotyluk]

I'm still new to Maven, so be patient...

After you have your artifact built, say foo.jar you have all the 
artifacts it depends on like bar.jar which are all scattered through 
~/.m2/...


If you want to write an installer for foo.jar, how do you collect all 
the dependencies like bar.jar together to distribute with your 
application installer?


In a similar fashion, when you do a release, don't you want to check all 
your dependent artifacts like bar.jar into source control so you can 
rebuild that release again without worrying that that version of bar.jar 
has vanished from all repositories on earth?


Cheers, Eric

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

Re: How to extend GWT Module to Dynamic Web Module with Maven?

[Wayne Fay]

> on the page:
> http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/39e0ff6325e4d504/55bfd342d77ec910?pli=1
>
> one explains how gwt-module can be extended to Dynamic Web Module in order
> to be deploybar into eclipse tomcat. I've configured my pom so, that item 3
> will be done by maven.

You will most likely have better luck getting these questions answered
at the GWT forum (or possibly even the M2E forum/list) than here at
Maven.

Wayne

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

Re: How to use wagon-ssh-external instead of wagon-ssh?

[Andreas Sewe]

Hi Wayne,


Well, there's always the "Version 99 does not exist" option...


that's something I couldn't get past Maven 3. Also tried 
true and a system-scoped dependency with an invalid 
, but to no avail.



Could you maybe set a dependency to that jar, and set the scope to
"runtime"? Don't know if that will help though.


No, it didn't. :-(

Thanks for the suggestions, though.

Andreas Sewe

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

How to extend GWT Module to Dynamic Web Module with Maven?

[sipungora]

Hi,

My problem:

on the page:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/39e0ff6325e4d504/55bfd342d77ec910?pli=1

one explains how gwt-module can be extended to Dynamic Web Module in order
to be deploybar into eclipse tomcat. I've configured my pom so, that item 3
will be done by maven.


3. insert the following natures into your .project file (inside the
natures node):
   
org.eclipse.wst.common.modulecore.ModuleCoreNature
   
org.eclipse.wst.common.project.facet.core.nature
org.eclipse.wst.jsdt.core.jsNature 

But how can I configure pom for 7 and 8 items?


6. right-click the project and select Properties -> Project Facets 
7. Check  'Java' and 'Dynamic Web Project'
8. Click 'further configuration available' and change the Content
Directory to 'war', to align with GWT's output 


This is my configuration:



org.apache.maven.plugins
maven-eclipse-plugin
2.8



org.eclipse.jdt.core.javabuilder


com.google.gdt.eclipse.core.webAppProjectValidator


com.google.gwt.eclipse.core.gwtProjectValidator




org.eclipse.jdt.core.javanature


com.google.gwt.eclipse.core.gwtNature


org.eclipse.wst.common.modulecore.ModuleCoreNature


org.eclipse.wst.common.project.facet.core.nature


org.eclipse.wst.jsdt.core.jsNature





com.google.gwt.eclipse.core.GWT_CONTAINER


org.eclipse.jdt.launching.JRE_CONTAINER



6.0
2.4
additionalProjectFacets>




But additionalProjectFacets have no effect.
If I do items 7 and 8 manually as it was described, the file
org.eclipse.wst.common.project.facet.core.xml will be created. Its content
is



  
  


But unfortunately this file will not be created by maven (I build with "mvn
eclipse:eclipse").

This was item 7.

About item 8 I have no ideas yet (I mean the build with maven).

Thanks in advance.
Best Regards.
-sipungora

--
View this message in context: 
http://maven.40175.n5.nabble.com/How-to-extend-GWT-Module-to-Dynamic-Web-Module-with-Maven-tp4365106p4365106.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

Re: gwt + jsf?

[sipungora]

Solution:

"mvn war:inplace"

this creates war(webapp) directory in my eclipse project. All
jar-dependencies will be copied into WEB-INF/lib. 

Exactly this webapp will be published in eclipse tomcat.

And if I test it, it works!

Cool.


--
View this message in context: 
http://maven.40175.n5.nabble.com/gwt-jsf-tp4363026p4365083.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

Re: How to use wagon-ssh-external instead of wagon-ssh?

[Wayne Fay]

> good point. Unfortunately, I don't see a way to do that. It looks like I can
> only use  to exclude *transitive* dependencies of a plugin. At
> least the following plugin dependencies clause doesn't work:

Well, there's always the "Version 99 does not exist" option...

Could you maybe set a dependency to that jar, and set the scope to
"runtime"? Don't know if that will help though.

Wayne

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

Re: How to use wagon-ssh-external instead of wagon-ssh?

[Andreas Sewe]

Hi Wendy,


thanks for your suggestion. I am afraid, it didn't help: When declaring a
plugin dependency, the maven-site-plugin now has both
org.apache.maven.wagon:wagon-ssh-external:jar:1.0-beta-7 and
org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-6 as a dependency, but it
still insists on using the latter for sftp URIs. :-(


Perhaps you need to exclude the one you don't want?  Maven doesn't
recognize one as a replacement for the other, it just sees two
separate artifacts.


good point. Unfortunately, I don't see a way to do that. It looks like I 
can only use  to exclude *transitive* dependencies of a 
plugin. At least the following plugin dependencies clause doesn't work:


  

  

  org.apache.maven.wagon
  wagon-ssh

  

  

org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[ERROR] 
'build.plugins.plugin[org.apache.maven.plugins:maven-site-plugin].dependencies.dependency.artifactId' 
for null:null:jar is missing. @ line 151, column 27
[ERROR] 
'build.plugins.plugin[org.apache.maven.plugins:maven-site-plugin].dependencies.dependency.groupId' 
for null:null:jar is missing. @ line 151, column 27
[ERROR] 
'build.plugins.plugin[org.apache.maven.plugins:maven-site-plugin].dependencies.dependency.version' 
for null:null:jar is missing. @ line 151, column 27


I am afraid this is an incarantion of 
. :-( Or am I mistaken?


Best wishes,

Andreas Sewe


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

Re: How to use wagon-ssh-external instead of wagon-ssh?

[Wendy Smoak]

On Mon, May 2, 2011 at 6:11 AM, Andreas Sewe
 wrote:
> thanks for your suggestion. I am afraid, it didn't help: When declaring a
> plugin dependency, the maven-site-plugin now has both
> org.apache.maven.wagon:wagon-ssh-external:jar:1.0-beta-7 and
> org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-6 as a dependency, but it
> still insists on using the latter for sftp URIs. :-(

Perhaps you need to exclude the one you don't want?  Maven doesn't
recognize one as a replacement for the other, it just sees two
separate artifacts.

-- 
Wendy

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

Re: Assembly Plugin Problem with multi module Project

[Dmitriy Neretin]

Well, we are migrating a very old project from ant to maven. It is a multi
module project (ca. 17 modules). We can already compile and use the whole
project, so we are sure that our new maven "multi-module-structure" works
right. The next target is that the project should be delivered as a set of
defined artifacts. These artifacts are: *.jars, *.xmls, *.xsds,
*.properties, javadocs etc. files from particular subprojects. They should
be ordered in the defined directory structure:

/root
  - directory1
 - artifact1
 - artifact2
 - ...
  - directory2
 - artifact1
 - artifact2
  ...

So my thoughts was: if I have a multi module project I should take a
moduleSet from an assembly plugin. And how you know it didn't work...

Our project structure looks like this:

/project
  - module1
   pom.xml
  - module2
   pom.xml
  - moduleX
   pom.xml
(parent)pom.xml

Parent POM is also referenced in the child POM's. How I configured my
assembly plugin you can read in the first e-mail...

Dmitriy

2011/5/1 Ron Wheeler 

> What are you trying to build?
> Unless you are building something that is really off-beat, you should just
> be able to follow best practices.
>
> Most people do not need to do what you are doing.
>
> You seem to heading down a bizarre development path that is likely not
> needed and going to set up a complex and fragile build system.
> Maven has Best Practices for all kinds of applications (from webapps to
> batch jobs to desktop apps) with sizes that range from 1 module to hundreds.
> Very few of them involve anything as complex as what you are building.
>
> You might take a minute to describe what you are trying to build and see if
> you get a simple solution.
>
> One of the problems in this forum is that some of the guys here can make
> Maven do almost anything.
> If you ask them a detailed technical question with no context, you will get
> a perfectly correct response that moves you forward.
> If you are going down the wrong path, rapid progress is not necessarily in
> your best interest.
>
> Take a step back and let the forum know what you are trying to build and
> how your sources are structured.
>
> Ron
>
>
> On 01/05/2011 9:50 AM, Dmitriy Neretin wrote:
>
>> I need not only dependenciesSets, but also fileSets...
>>
>> 2011/4/28 Anders Hammar
>>
>>  You should not traverse the file structure but rely on dependencies! It
>>> should work building when just checking out this specific module from
>>> scm.
>>>
>>> /Anders
>>>
>>> On Thu, Apr 28, 2011 at 18:01, Dmitriy Neretin<
>>> dmitriy.nere...@googlemail.com>  wrote:
>>>
>>>  Holy sh... :)) Of cource it works :) But it is not really that what I
 wanted
 but it's not important now :) Thank you very much. But I still don't
 understand why the moduleSet didn't work... Strange (How old is the
 maven
 documentation). With this variable ${project.parent.basedir} I can

>>> get
>>>
 access on parent directory structure. So I hope to solve my problems
 completly!

 Have a nice day!

 2011/4/28 Anders Hammar

  No, you should not use moduleSet but dependencySet (or similar, I'm not
>
 at

> my computer and cannot check syntax).
>
> /Anders (mobile)
> Den 28 apr 2011 17.14 skrev "Dmitriy Neretin"<
> dmitriy.nere...@googlemail.com>:
>
>> Well I just removed the assembly declaration from the parent POM. I
>>
> just

> left there the new distribution module. When I change to the
>>
> distribution

> folder and execute mvn assembly:single or mvn clean package I get
>>
> this:
>>>
 [INFO] Reading assembly descriptor: config/assembly.xml
>> [WARNING] The following patterns were never triggered in this
>>
> artifact
>>>
 inclusion filter:
>> o 'A'
>>
>> [WARNING] The following patterns were never triggered in this
>>
> artifact
>>>
 inclusion filter:
>> o 'A'
>>
>> [WARNING] NOTE: Currently, inclusion of module dependencies may
>>
> produce
>>>
 unpredictable results if a version conflict occu
>> rs.
>> [INFO]
>>
>> 

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

> [INFO] Failed to create assembly: Error creating assembly archive
>>
> test:
>>>
 You
>
>> must set at least one file.
>>
>> Well the descriptor war reas only once, but we still see the double
>>
> warning
>
>> about failed trigger :(
>>
>> But the assembly configuration is right:
>>
>> 
>> 
>> true
>> 
>> A
>> 
>> 
>> tools/caseviewer
>> false
>> 
>> 
>

Re: How to use wagon-ssh-external instead of wagon-ssh?

[Andreas Sewe]

Hi Brett,


I think in the Maven 3 version of the site plugin, you need to add
the wagon as a dependency of the site plugin, instead of as an
extension (which only applies to the core deployment components).


thanks for your suggestion. I am afraid, it didn't help: When declaring 
a plugin dependency, the maven-site-plugin now has both 
org.apache.maven.wagon:wagon-ssh-external:jar:1.0-beta-7 and 
org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-6 as a dependency, but it 
still insists on using the latter for sftp URIs. :-(


Any other suggestions?

Andreas Sewe


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

Re: gwt + jsf?

[Wayne Fay]

> My problem now is, how can I configure my pom so, that the jar will be in
> WEB-INF/lib of my war?
> Currently I do it manually.

Posting this question reveals that you don't understand the very basic
fundamental concepts of Maven. Go back to the beginning, read the
documentation on the website, do the Maven in 5 minutes and Maven in
30 minutes exercises, grab one of the free ebooks on Maven and work
through a sample project or two, and then come back when you have real
questions.

Wayne

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