Hmm, Googel decided to send my mail before I finished...
> I ran into something similar in the maven-war-project. Checking I see that
> similar hard-coded values exist there:
>
Here's the link:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-war-plugin/src/test/java/org/apache/maven/plugin
I ran into something similar in the maven-war-project. Checking I see that
similar hard-coded values exist there:
On Mon, Nov 24, 2014 at 9:03 AM, Karl Heinz Marbaise
wrote:
> Hi,
>
> so after diving more into this issue i found that the original
> MavenProject is working different than the impl
Hi,
so after diving more into this issue i found that the original
MavenProject is working different than the implemented Stub
(MavenProjectBasicStub), cause the MavenProject#getArtifactId() method
looks like this:
public String getArtifactId()
{
return getModel().getArtifact
Hi,
On 11/23/14 10:27 AM, Michael Osipov wrote:
Am 2014-11-22 um 20:58 schrieb Karl Heinz Marbaise:
Hi,
i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
maven-archiver-2.6and i'm currently faced with a puzzling
situation...
If i update to 2.6 several tests will fail...
F
Am 2014-11-22 um 20:58 schrieb Karl Heinz Marbaise:
Hi,
i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
maven-archiver-2.6and i'm currently faced with a puzzling situation...
If i update to 2.6 several tests will fail...
For the tests there were stubs generated which usin
Hi,
i'm trying to upgrade maven-ejb-plugin from maven-archiver 2.5 to
maven-archiver-2.6and i'm currently faced with a puzzling situation...
If i update to 2.6 several tests will fail...
For the tests there were stubs generated which using groupId/artifactId
etc. but if i update to 2.6 i
