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 ./${basedir}/target to . (so it is
now at the same depth as ${basedir}). Did a mvn package and the build
succeeds! My conclusion, is that the problem arises from those relative
paths in the build.xml file below.
Adrian.
Here is the feature's pom.xml:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>com.acme.lang.eclipse</groupId>
<artifactId>acme-lang-eclipse</artifactId>
<version>1.0-alpha-1</version>
</parent>
<groupId>com.acme.lang.eclipse.feature</groupId>
<artifactId>acme-lang-eclipse-feature</artifactId>
<version>1.0-alpha-1-SNAPSHOT</version>
<packaging>zip</packaging>
<name>acme Language Feature for Eclipse</name>
<description>Integrates acme projects into the Eclipse IDE.</description>
<scm>
<connection>scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature</connection>
<developerConnection>scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature</developerConnection>
<url>https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature</url>
</scm>
<repositories>
<repository>
<id>hosted-projects.com</id>
<name>Central acme Repository</name>
<url>https://someserver.com:443/dav/acme/repository</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>[EMAIL PROTECTED]</id>
<name>Central acme Repository</name>
<url>https://someserver.com:443/dav/acme/snapshots</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>pde-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<eclipseInstall>${eclipse.home}</eclipseInstall>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<downloadSources>true</downloadSources>
<additionalProjectnatures>
<projectnature>org.eclipse.pde.FeatureNature</projectnature>
</additionalProjectnatures>
<additionalBuildcommands>
<buildcommand>org.eclipse.pde.FeatureBuilder</buildcommand>
</additionalBuildcommands>
</configuration>
</plugin>
</plugins>
</build>
</project>
Dan Tran wrote:
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 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 under an Eclipse instance -- great!
I am looking in the ${basedir}/build.xml file and I see this section:
<target name="@dot" depends="init" unless="@dot"
description="Create
jar: com.acme.lang.eclipse.editors @dot.">
<delete dir="${temp.folder}/@dot.bin"/>
<mkdir dir="${temp.folder}/@dot.bin"/>
<path id="@dot.classpath">
<pathelement
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.ui_3.2.0.I20060605-
1400.jar"/>
<pathelement
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar"/>
<pathelement
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060601.jar"/>
<pathelement
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar"/>
<pathelement
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar"/>
The relative paths here are causing the problem... Is there some way to
regenerate the build.xml during Maven builds? Any other solution?...
Adrian.
Dan Tran wrote:
> 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
>> 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 that the build.xml file cannot
be
>> run outside of the ${basedir} directory...
>>
>> Any workaround for this situation?
>> How about tweaking the release:perform goal?
>>
>> Adrian.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
