2008/9/19 Tomek Maciejewski [EMAIL PROTECTED]:
...
classpathContainers
classpathContainerorg.elipse.mtj.JavaMEContainer/Sun
Java(TM) Wireless Toolkit 2.5.2 for
CLDC/DefaultColorPhone/classpathContainer
/classpathContainers
David,
this gave me hard time too. After a while I realized, that profiles
can only be activated by *system* properties which is a different
beast than those properties one can define in a POM or the settings.
System properties are those which are provided to maven by the command
line parameter
So you want to add another folder as container for source files?
(additionally to /src/main/java and /target/generated-sources). Good
question..
From what google points me to i would recommend you to have a look at
http://mojo.codehaus.org/build-helper-maven-plugin/index.html . I do not
know, if
David,
2008/9/19 David C. Hicks [EMAIL PROTECTED]:
I'm beginning a new, fairly large, project. Eclipse will be our development
platform, but I've already set up the starting point in Maven. Simple
enough. Now, my question is, how can I keep them in sync, easily? I
realize that it's best
I have this declaration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
executions
execution
idunit-tests/id
phasetest/phase
Hi James,
First you should know there's a specific mailing list for M2E. You should be
able to find more accurate answer on this list.
Second, could you please give us more details about what it's doing
incorrectly. Actually it would help that you both explain what it does now
and what you think
No, this requires upgrading maven to use a new container with a different api,
which is why we never put it into 2.0. 3.0 would be the first release to
reasonable expect it to be fixed. I worked around it by rebuilding that jar
without the warning and distributed it across my team, but then one
I'm forced to go with 1.5.1 right now, so here is a workaround that worked
for me (on gentoo):
* Checkout a working copy with svn client 1.5.1, otherwise svn copy fails
with file already exists
* run mvn release:prepare, it will fail in the svn --non-interactive copy
...
* run svn update
*
Thanks again. I'll check out the build-helper plugin.
As for larger projects, that's exactly how I've done them in the past.
It requires a little massaging of the pom.xml files, but I haven't found
a cleaner way to handle it. Maybe one day between Eclipse and Maven
this won't be such a
Greetings,
I don't see any way for me to customize the generated PMD report to my
needs. Specifically, I think it would be quite helpful to me and my
project developers to have clickable rules which would launch to the
official PMD documentation for the rule which is being reported. I
believe
Problem was in fact that test from one module was referencing a test
resource from other module of the same maven multi-module project. I'm not
sure whether it is a bug in TestNG or m2eclipse eclipse integration, but it
enabled test, which was failing in Maven, to run successfully from TestNG
David C. Hicks wrote:
Thanks again. I'll check out the build-helper plugin.
As for larger projects, that's exactly how I've done them in the past.
It requires a little massaging of the pom.xml files, but I haven't found
a cleaner way to handle it. Maybe one day between Eclipse and
It may just be me, but I don't understand what exactly you are asking.
Perhaps you can describe things in more detail, and someone will reply
with a reasonable approach.
In the meantime, if you haven't already read either of the freely
available Maven2 PDF ebooks, you really should:
Test resources are not typically available in the packaged jars
produced by a given module.
Given what you've said (now that you've solved it), you should
probably look at creating a module with packaging test-jar that
bundles up the test resources you need to use across multiple modules.
Then
Yes Wayne, thank you, I know, moving shared test resources into separate
module solved it for me. Problem that remains is why was test resource
available in TestNG plugin when it shouldn't have. For this problem I've
moved discussion to m2eclipse user mailing list, as I suspect it wrongly set
Hi all,
I have written an archetype and deployed to my remote repository.
The repository requires authentication.
The problem is when somebody runs mvn archetype:generate ...
-DarchetypeRepository=http://my.repo he gets a 401 from the server and
generation fails of course.
Is there any
--- On Sat, 9/20/08, Adrian Herscu wrote:
I have written an archetype and deployed to my remote
repository.
The repository requires authentication.
The problem is when somebody runs mvn archetype:generate
...
-DarchetypeRepository=http://my.repo he gets a 401 from the
server and
Good points, Eugene. I'll take a closer look at what we're trying to
accomplish. Maybe it does make more sense to put integration tests in a
different module. This is a very new project, so we're still figuring
out a lot of the details. It's just so easy to add source folders under
18 matches
Mail list logo
