Anyone? :-)
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Dienstag, 23. Oktober 2012 16:53
An: users@maven.apache.org
Betreff: dependency:unpack doesn't work correctly with Nexus, SNAPSHOT and
classifier?
Hi
First of all I'd like to ask you to be
Hi John,
John Kramer wrote:
Hey guys,
I have a question regarding the maven dependencies section.
In order to put a dependency on a test jar, is it correct to specify
typetest-jar/type or typetest/type?
test-jar, test does not exist. However, I typically declare always both:
type and
Hi John,
the problem is that Eclipse doesn't know any difference between the normal
classpath of an application and a test classpath that includes tests. For
eclipse everything (application and test classes) are thrown into one basket.
That's why you are able to build in Eclipse. As Jörg
It could be that you hit https://jira.codehaus.org/browse/MNG-5324
Robert
Op Fri, 26 Oct 2012 08:53:51 +0200 schreef Lewis, Eric eric.le...@ipi.ch:
Anyone? :-)
-Ursprüngliche Nachricht-
Von: Lewis, Eric [mailto:eric.le...@ipi.ch]
Gesendet: Dienstag, 23. Oktober 2012 16:53
An:
Robert
can anton commit his 2 patches (with the Testcase) and get this resolved?
Thanks!
Martin Gainty
__
Note de déni et de confidentialité
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te
Hi Chris and everyone,
the problem is that Eclipse doesn't know any difference between the
normal classpath of an application and a test classpath that includes
tests. For eclipse everything (application and test classes) are thrown
into one basket. That's why you are able to build in Eclipse.
Deploy macker-rules.xml to repository.
Use m-dependency-p to fetch these rules from repo during build.
Configure m-macker-p to pick up rule file where m-dependency-p put it.
Am 26.10.2012 20:04 schrieb Alberto Ivo alberto...@gmail.com:
I know there is a specific discussion list for Macker but
I guess the Maven Remote Resources Plugin could be used as well. But
it depends on if the macker rules file has to be in src/main/resources
or if it could be somewhere else.
/Anders
On Fri, Oct 26, 2012 at 8:57 PM, Ansgar Konermann
ansgar.konerm...@googlemail.com wrote:
Deploy macker-rules.xml
According to the Macker usage, the macker-rules.xml MUST be in the
scr/main/resource.
Ansgar, I liked you idea but I'm still very noob to understand how to do
it. I will research about that.
Ivo
On Fri, Oct 26, 2012 at 5:03 PM, Anders Hammar and...@hammar.net wrote:
I guess the Maven Remote
If it has to be in src/main/resources I guess you're out of luck. It's
technically possible to have a rules file copied to that folder during
the build process, but it's against the Maven laws. Anything
copied/generated during the build process should be to the target
folder.
Please note that the
Martin,
I've managed to write a test, but wasn't able to reproduce the issue.
The fix from Anton translates the uniqueVersion back to the nonUnique
version, so Aether is responsible for resolving it back to the right
version. The real cause happened already somewhere earlier, we need to
hmmm.. I got it now.
Thanks Anders!
Ivo
On Fri, Oct 26, 2012 at 6:46 PM, Anders Hammar and...@hammar.net wrote:
If it has to be in src/main/resources I guess you're out of luck. It's
technically possible to have a rules file copied to that folder during
the build process, but it's against
my problem is not simple to explain.
globally, here is it : I want to deploy on heroku (in the cloud) a scala
project, with the support of vaadin (web framework).
for vaadin, I assume there is no problem.
when I try to deploy my project on heroku, I have an error like this :
13 matches
Mail list logo