Another interesting discovery... Checked out the project in a different
directory with a different depth, did a mvn package and the build.xml
file was updated according to the new directory depth. Why it does not
happen during the release:perform build?!
Anyway, I have found a temporary soluti
I am aware about there are some badly coded Java programs that cannot
deal with spaces in Windoze paths... Therefore I am using only the short
DOS notation (PROGRA~1 instead of "Program Files").
I have only one feature -- its pom.xml is appended below.
I moved the checkout directory from ./${b
how many features you do you have? could you post the pom on for the
feature?
I see you are using Program Files on your path , this make me nervous, even
thou it should work :-)
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi Dan, and thanks for the fast reply!
I have followed th
Hi Dan, and thanks for the fast reply!
I have followed the project structure from the pde-maven-plugin guide:
parent
+features
some.feature
+plugins
some.plugin
another.plugin
I have no problems during normal builds. The artifact is created and I
can deploy and run it
and you have no problem during normal build?
what does your projects structure look like?
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I am trying to release my Eclipse plugins and I am getting lots of "The
import some.eclipse.package cannot be resolved" compilation errors
Hi all,
I am trying to release my Eclipse plugins and I am getting lots of "The
import some.eclipse.package cannot be resolved" compilation errors
during the release:perform goal.
I have tried to run mvn package on the target/checkout directory and I
am getting the same errors... It seems th
