| Headless Buckminster for 3.4 [message #19307] |
Thu, 05 June 2008 15:25  |
|
Hi,
There was some problems with the headless Buckminster for 3.4. The
problem was caused by archive entries in our headless-site.xml file that
appointed entries in the Eclipse 3.4 platform. This was not so bright
since the platform is a moving target right now. When the RC3 was
released, some of the links broke.
To remedy this, our 3.4 update site now contains copies of the platform
plug-ins instead of links. A new version was pushed to our update site
about 30 minutes ago and should be available on all mirrors real soon.
I'm sorry for the inconvenience.
Regards,
Thomas Hallgren
|
|
|
| Re: Headless Buckminster for 3.4 [message #19539 is a reply to message #19307] |
Wed, 11 June 2008 09:23  |
Eclipse User |
|
|
|
Originally posted by: klammer.utanet.at
Hi,
following exception occurs when trying to build product via headless
buckminster (for 3.4). Building with 'normal' Buckminster via UI is working.
Does anybody have a clue on that? What are the differences (are there
any) between headless and 'normal' regarding this problem?
[java] java.lang.IllegalArgumentException: Illegal group reference
[java] at java.util.regex.Matcher.appendReplacement(Matcher.java:713)
[java] at java.util.regex.Matcher.replaceFirst(Matcher.java:861)
[java] at java.lang.String.replaceFirst(String.java:2147)
[java] at
org.eclipse.buckminster.ant.tasks.VersionQualifierTask.repla ceQualifier(VersionQualifierTask.java:109)
[java] at
org.eclipse.buckminster.pde.tasks.FeatureConsolidator.run(Fe atureConsolidator.java:383)
[java] at
org.eclipse.buckminster.pde.ant.FeatureConsolidatorTask.exec ute(FeatureConsolidatorTask.java:100)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
[java] at org.apache.tools.ant.Task.perform(Task.java:348)
[java] at org.apache.tools.ant.Target.execute(Target.java:357)
[java] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[java] at
org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
[java] at
org.apache.tools.ant.Project.executeTarget(Project.java:1298 )
[java] at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
[java] at
org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
[java] at
org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
[java] at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:623)
[java] at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:456)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:282 )
[java] at
org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:162)
[java] at
org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:128)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:146)
[java] at
org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:75)
[java] at
org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:68)
[java] at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:45)
[java] at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:80)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 88)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 22)
[java] at
org.eclipse.buckminster.cmdline.Headless.start(Headless.java :113)
[java] at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:379)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
[java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
[java] at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
[java] at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
thx,
Claus Klammer
Thomas Hallgren schrieb:
> Hi,
> There was some problems with the headless Buckminster for 3.4. The
> problem was caused by archive entries in our headless-site.xml file that
> appointed entries in the Eclipse 3.4 platform. This was not so bright
> since the platform is a moving target right now. When the RC3 was
> released, some of the links broke.
>
> To remedy this, our 3.4 update site now contains copies of the platform
> plug-ins instead of links. A new version was pushed to our update site
> about 30 minutes ago and should be available on all mirrors real soon.
>
> I'm sorry for the inconvenience.
>
> Regards,
> Thomas Hallgren
|
|
|
| Re: Headless Buckminster for 3.4 [message #19584 is a reply to message #19539] |
Wed, 11 June 2008 10:05 |
|
Hi Claus,
There should not be any difference in this respect between a headless
build and an IDE build. The only thing I can think of is if you use
different property settings for the version qualifier so that the
generated qualifier contains dollar signs followed by digits. The
String.replaceFirst(pattern, replacement) will treat those as group
references and fail with the exception that you encounter.
Are you perhaps passing a generator.lastRevision or
generator.lastModified properties on the command line so that they are
subject to shell expansion?
Regards,
Thomas Hallgren
Claus Klammer wrote:
> Hi,
> following exception occurs when trying to build product via headless
> buckminster (for 3.4). Building with 'normal' Buckminster via UI is
> working.
> Does anybody have a clue on that? What are the differences (are there
> any) between headless and 'normal' regarding this problem?
>
> [java] java.lang.IllegalArgumentException: Illegal group reference
> [java] at
> java.util.regex.Matcher.appendReplacement(Matcher.java:713)
> [java] at java.util.regex.Matcher.replaceFirst(Matcher.java:861)
> [java] at java.lang.String.replaceFirst(String.java:2147)
> [java] at
> org.eclipse.buckminster.ant.tasks.VersionQualifierTask.repla ceQualifier(VersionQualifierTask.java:109)
>
> [java] at
> org.eclipse.buckminster.pde.tasks.FeatureConsolidator.run(Fe atureConsolidator.java:383)
>
> [java] at
> org.eclipse.buckminster.pde.ant.FeatureConsolidatorTask.exec ute(FeatureConsolidatorTask.java:100)
>
> [java] at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:597)
> [java] at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.Target.execute(Target.java:357)
> [java] at
> org.apache.tools.ant.Target.performTasks(Target.java:385)
> [java] at
> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
> [java] at
> org.apache.tools.ant.Project.executeTarget(Project.java:1298 )
> [java] at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>
> [java] at
> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>
> [java] at
> org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
> [java] at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:623)
>
> [java] at
> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:456)
>
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:597)
> [java] at
> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:282 )
> [java] at
> org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:162)
>
> [java] at
> org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:128)
>
> [java] at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:146)
>
> [java] at
> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:75)
>
> [java] at
> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:68)
> [java] at
> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:45)
>
> [java] at
> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:80)
>
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 88)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 22)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :113)
> [java] at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:379)
>
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> [java] at java.lang.reflect.Method.invoke(Method.java:597)
> [java] at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
> [java] at
> org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>
> thx,
> Claus Klammer
>
> Thomas Hallgren schrieb:
>> Hi,
>> There was some problems with the headless Buckminster for 3.4. The
>> problem was caused by archive entries in our headless-site.xml file
>> that appointed entries in the Eclipse 3.4 platform. This was not so
>> bright since the platform is a moving target right now. When the RC3
>> was released, some of the links broke.
>>
>> To remedy this, our 3.4 update site now contains copies of the
>> platform plug-ins instead of links. A new version was pushed to our
>> update site about 30 minutes ago and should be available on all
>> mirrors real soon.
>>
>> I'm sorry for the inconvenience.
>>
>> Regards,
>> Thomas Hallgren
>
|
|
|
| Re: Headless Buckminster for 3.4 [message #19629 is a reply to message #19584] |
Wed, 11 June 2008 10:58 |
| Eclipse User |
|
|
|
Originally posted by: klammer.utanet.at
Hi Thomas,
thanks for the hint. We indeed use the variable 'qualifier'in our
scripts which is not set when building locally.
-------- begin snippet -------------
<arg value=""qualifier.replacement.*=${qualifier}" " />
---------- end snippet ------------
Setting a value fixed the problem.
Cheers,
Claus
Thomas Hallgren schrieb:
> Hi Claus,
> There should not be any difference in this respect between a headless
> build and an IDE build. The only thing I can think of is if you use
> different property settings for the version qualifier so that the
> generated qualifier contains dollar signs followed by digits. The
> String.replaceFirst(pattern, replacement) will treat those as group
> references and fail with the exception that you encounter.
>
> Are you perhaps passing a generator.lastRevision or
> generator.lastModified properties on the command line so that they are
> subject to shell expansion?
>
> Regards,
> Thomas Hallgren
>
>
>
> Claus Klammer wrote:
>> Hi,
>> following exception occurs when trying to build product via headless
>> buckminster (for 3.4). Building with 'normal' Buckminster via UI is
>> working.
>> Does anybody have a clue on that? What are the differences (are there
>> any) between headless and 'normal' regarding this problem?
>>
>> [java] java.lang.IllegalArgumentException: Illegal group reference
>> [java] at
>> java.util.regex.Matcher.appendReplacement(Matcher.java:713)
>> [java] at java.util.regex.Matcher.replaceFirst(Matcher.java:861)
>> [java] at java.lang.String.replaceFirst(String.java:2147)
>> [java] at
>> org.eclipse.buckminster.ant.tasks.VersionQualifierTask.repla ceQualifier(VersionQualifierTask.java:109)
>>
>> [java] at
>> org.eclipse.buckminster.pde.tasks.FeatureConsolidator.run(Fe atureConsolidator.java:383)
>>
>> [java] at
>> org.eclipse.buckminster.pde.ant.FeatureConsolidatorTask.exec ute(FeatureConsolidatorTask.java:100)
>>
>> [java] at
>> org.apache.tools.ant.UnknownElement.execute(UnknownElement.j ava:288)
>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [java] at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> [java] at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:597)
>> [java] at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(Dispatch Utils.java:105)
>>
>> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
>> [java] at org.apache.tools.ant.Target.execute(Target.java:357)
>> [java] at
>> org.apache.tools.ant.Target.performTasks(Target.java:385)
>> [java] at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.ja va:1329)
>> [java] at
>> org.apache.tools.ant.Project.executeTarget(Project.java:1298 )
>> [java] at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(D efaultExecutor.java:41)
>>
>> [java] at
>> org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.exe cuteTargets(EclipseDefaultExecutor.java:32)
>>
>> [java] at
>> org.apache.tools.ant.Project.executeTargets(Project.java:118 1)
>> [java] at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:623)
>>
>> [java] at
>> org.eclipse.ant.internal.core.ant.InternalAntRunner.run(Inte rnalAntRunner.java:456)
>>
>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [java] at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> [java] at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:597)
>> [java] at
>> org.eclipse.buckminster.ant.AntRunner.run(AntRunner.java:282 )
>> [java] at
>> org.eclipse.buckminster.ant.actor.AntActor.internalPerform(A ntActor.java:162)
>>
>> [java] at
>> org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:128)
>>
>> [java] at
>> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:146)
>>
>> [java] at
>> org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:75)
>>
>> [java] at
>> org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:68)
>>
>> [java] at
>> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:45)
>>
>> [java] at
>> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:80)
>>
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 88)
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 22)
>> [java] at
>> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :113)
>> [java] at
>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
>>
>> [java] at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher..java:110)
>>
>> [java] at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>>
>> [java] at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:379)
>>
>> [java] at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>>
>> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> [java] at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> [java] at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> [java] at java.lang.reflect.Method.invoke(Method.java:597)
>> [java] at
>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
>> [java] at
>> org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
>> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
>> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>>
>> thx,
>> Claus Klammer
>>
>> Thomas Hallgren schrieb:
>>> Hi,
>>> There was some problems with the headless Buckminster for 3.4. The
>>> problem was caused by archive entries in our headless-site.xml file
>>> that appointed entries in the Eclipse 3.4 platform. This was not so
>>> bright since the platform is a moving target right now. When the RC3
>>> was released, some of the links broke.
>>>
>>> To remedy this, our 3.4 update site now contains copies of the
>>> platform plug-ins instead of links. A new version was pushed to our
>>> update site about 30 minutes ago and should be available on all
>>> mirrors real soon.
>>>
>>> I'm sorry for the inconvenience.
>>>
>>> Regards,
>>> Thomas Hallgren
>>
|
|
|
Powered by
FUDForum. Page generated in 0.02349 seconds
] 
Search
Help
Register
Login
Home
