I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.
On Fri, Sep 23, 2011 at 8:01 AM, Barrie Treloar baerr...@gmail.com wrote:
Does anyone actually use pde mode in maven-eclipse-plugin?
The support looks pretty
Carlos Sanchez wrote:
I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.
+1
- Jörg
-
To unsubscribe, e-mail:
See this post for more infos:
http://stackoverflow.com/questions/6336340/with-the-maven-release-plugin-how-to-branch-a-module-and-its-children
-Original Message-
From: Laird Nelson [mailto:ljnel...@gmail.com]
Sent: 26 September 2011 20:58
To: Maven Users List
Subject: Question about SCM
Hi,
I have some classes and some junit test classes for them.I'm running the
junit test which is working fine in eclipse.I have also created a maven
quickstart archetype.Inside main java i have put my source for java
code and inside test java i have kept junit test classes.But when I try
to
On Tue, Sep 27, 2011 at 4:20 PM, arka.sharma arka.sharma1...@gmail.com wrote:
Hi,
I have some classes and some junit test classes for them.I'm running the
junit test which is working fine in eclipse.I have also created a maven
quickstart archetype.Inside main java i have put my source for
*Surefire Report
Summary
Tests Errors FailuresSkipped Success RateTime
0 0 0 0 0% 0
Note: failures are anticipated and checked for with assertions while errors
are unanticipated.*
This is the report t*arget/site/surefire-report.html* after doing *mvn
Thank you for pointing out to that discussion. Even though I don't agree
completely - if running the coverage tool Cobertura changes the status of
your tests, I'd say that in most likelihood the problem should be cobertura
and not your code or your test - I might live with running the cobertura
Hi,
i have a project which produces a ear file but the problem i've encountered
is that the generated ear file can't be extracted via jar -x file.ear nor
can i list the contents of the archive via jar -t file.ear
I've tested it with a unzip tool on command line which works without any
problems
In my experience you have:
* a 40% chance of the failure being a bad test
* a 40% chance of the failure being a bug in your production code
* a 20% chance of the failure being a side-effect of instrumentation
which invalidates the test
If you and all the developers in your team cannot
+1
Having fewer partial implementations to confuse folks is always better IMO.
On 9/27/11 2:08 AM, Carlos Sanchez wrote:
I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.
On Fri, Sep 23, 2011 at 8:01 AM,
You might want to try the following:
if you don't already have a global pom properties tag you would add one.
Then in the body of the properties tag you would add the following 2
tags and their values:
properties
surefire.useFilefalse/surefire.useFile
Is there an easy way to see from the command line which repository an
artifact is being resolved to/from?
On Thu, Sep 22, 2011 at 11:03 PM, Wayne Fay wayne...@gmail.com wrote:
Downloaded: http://
SERVER/nexus/content/groups/public/org/springframework/spring-web/maven-metadata.xml
Is there
Also, I'm not convinced it's a nexus thing.
I've removed (completely) the local storage for repo1 (where this artifact
is proxied from).
I think it has to do with this dependency chain:
[DEBUG]com.sun.jersey.contribs:jersey-spring:jar:1.4:compile
[DEBUG]
Hello,
I have the same need as this one described in this post. Have you found a
solution?
Thanks.
--
View this message in context:
http://maven.40175.n5.nabble.com/Integration-of-an-applet-jar-in-a-war-with-Eclipse-Maven-integration-WTP-plugins-tp127771p4846754.html
Sent from the Maven -
Are you by any chance using version ranges in any of your poms - that tends to
cause maven to repeatedly download the metadata when checking for newer
versions to satisfy your ranges.
On 28/09/2011, at 7:37 AM, Maven User wrote:
Is there an easy way to see from the command line which
This is not a maven problem.
It looks like a failure to read the documentation for the jar command.
Try
jar -xf file.ear
or
jar -tf file.ear
On 27/09/2011, at 9:29 PM, Karl Heinz Marbaise wrote:
Hi,
i have a project which produces a ear file but the problem i've
FWIW, we're using pde mode at present.
We have a largish (~ 40 modules) framework that builds both RCP applications
and web applications.
I haven't had a chance to figure out how to integrate Tycho into this
arrangement. On the surface it looks like you're either using p2 dependencies
or
On Wed, Sep 28, 2011 at 11:40 AM, Stephen Coy st...@resolvesw.com wrote:
FWIW, we're using pde mode at present.
We have a largish (~ 40 modules) framework that builds both RCP applications
and web applications.
I haven't had a chance to figure out how to integrate Tycho into this
We're building bundles with the following build configuration:
packagingbundle/packaging
build
extensions
extension
groupIdorg.apache.felix/groupId
artifactIdorg.osgi.core/artifactId
version1.2.0/version
Thanks for affirming this Ron. By the way, how do you ensure that all
those projects depend on the same set of external dependences without
duplicating the information for each POM?
Cheers,
Behrang Saeedzadeh
http://www.behrang.org
On Tue, Sep 27, 2011 at 2:17 AM, Ron Wheeler
20 matches
Mail list logo
