[JBoss JIRA] (JBDS-2460) replace included p2-director.zip with upstream version from tycho-standalone-p2-director
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2460?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2460:
--------------------------------------
[~dgolovin]: so we agree that we cannot replace this p2 director by Tycho one since it has to be included in installer. Am I right?
If yes, I think we should close this issue as invalid, or rename it to a more meaningful improvement ("replace included p2-director.zip by a Maven dependency" or something like that)
> replace included p2-director.zip with upstream version from tycho-standalone-p2-director
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-2460
> URL: https://issues.jboss.org/browse/JBDS-2460
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyDependencies, Build, installer
> Affects Versions: 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 7.0.0.Alpha2
>
>
> To build JBDS installer we need p2-director.zip [0], which is 9M and doesn't include sources. Ideally, we could just use something from Eclipse.org at build-time, and COULD include sources.
> [0] https://svn.jboss.org/repos/devstudio/trunk/product/installer/p2-director...
> I looked at tycho-standalone-p2-director [1,2] but it's only an update site -- it lacks equinox.launcher fragments for the various platforms on which we run.
> [1] https://github.com/eclipse/tycho/tree/master/tycho-bundles/tycho-standalo...
> [2] http://search.maven.org/remotecontent?filepath=org/eclipse/tycho/tycho-st...
> So... maybe we need to do something similar but include the binary bits too, so that we can produce something similar to what's in this zip [3] ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBIDE-13706) Cannot install Google tools from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13706?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13706:
-----------------------------------
Description:
Here is what log says:
{code}
Contains: Cannot complete the install because one or more required items could not be found.
Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found
Contains: Cannot satisfy dependency:
Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919
{code}
Main message: *requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found*
was:
Here is what log says:
{code}
Contains: Cannot complete the install because one or more required items could not be found.
Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found
Contains: Cannot satisfy dependency:
Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919
{code}
> Cannot install Google tools from Central
> ----------------------------------------
>
> Key: JBIDE-13706
> URL: https://issues.jboss.org/browse/JBIDE-13706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> Here is what log says:
> {code}
> Contains: Cannot complete the install because one or more required items could not be found.
> Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
> Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found
> Contains: Cannot satisfy dependency:
> Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
> Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919
> {code}
> Main message: *requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found*
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBIDE-13706) Cannot install Google tools from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13706?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13706:
-----------------------------------
Description:
Here is what log says:
{code}
Contains: Cannot complete the install because one or more required items could not be found.
Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found
Contains: Cannot satisfy dependency:
Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919
{code}
> Cannot install Google tools from Central
> ----------------------------------------
>
> Key: JBIDE-13706
> URL: https://issues.jboss.org/browse/JBIDE-13706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> Here is what log says:
> {code}
> Contains: Cannot complete the install because one or more required items could not be found.
> Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
> Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found
> Contains: Cannot satisfy dependency:
> Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711)
> Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBIDE-13666) Error when renaming a domain with 1+ applications
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13666?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13666:
-------------------------------------------------
qgong(a)redhat.com <qgong(a)redhat.com> made a comment on [bug 916330|https://bugzilla.redhat.com/show_bug.cgi?id=916330]
Verified on the env that migrate from devenv_stage_312 to devenv_2888
1.Create domain
curl -k --user "qgong+1@redhat.com:111111" -H "Accept: application/xml" https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/ -X POST --form id=bingobongo
2.Create jbossas-7 application
curl -k --user "qgong+1@redhat.com:111111" -H "Accept: application/xml" https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/bin... -X POST -v --form name=as --form cartridge=jbossas-7
3.update domain
[qgong@dhcp-8-169 python1]$ curl -k --user "qgong+1@redhat.com:111111" -H "Accept: application/xml" https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/bin... -X PUT --form id=honkabonka -v
* About to connect() to proxy file.rdu.redhat.com port 3128 (#0)
* Trying 10.11.255.147... connected
* Connected to file.rdu.redhat.com (10.11.255.147) port 3128 (#0)
* Establish HTTP proxy tunnel to ec2-23-22-110-226.compute-1.amazonaws.com:443
* Server auth using Basic with user 'qgong+1(a)redhat.com'
> CONNECT ec2-23-22-110-226.compute-1.amazonaws.com:443 HTTP/1.1
> Host: ec2-23-22-110-226.compute-1.amazonaws.com:443
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.13.1.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2
> Proxy-Connection: Keep-Alive
> Accept: application/xml
>
< HTTP/1.0 200 Connection established
<
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* warning: ignoring value of ssl.verifyhost
* skipping SSL peer certificate verification
* SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
* Server certificate:
* subject: E=root@ip-10-98-59-17,CN=ip-10-98-59-17,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
* start date: Feb 27 05:30:45 2013 GMT
* expire date: Feb 27 05:30:45 2014 GMT
* common name: ip-10-98-59-17
* issuer: E=root@ip-10-98-59-17,CN=ip-10-98-59-17,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=--
* Server auth using Basic with user 'qgong+1(a)redhat.com'
> PUT /broker/rest/domains/bingobongo HTTP/1.1
> Authorization: Basic cWdvbmcrMUByZWRoYXQuY29tOjExMTExMQ==
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.13.1.0 zlib/1.2.3 libidn/1.18 libssh2/1.2.2
> Host: ec2-23-22-110-226.compute-1.amazonaws.com
> Accept: application/xml
> Content-Length: 147
> Expect: 100-continue
> Content-Type: multipart/form-data; boundary=----------------------------7f17e29ca364
>
< HTTP/1.1 100 Continue
< HTTP/1.1 100 Continue
< HTTP/1.1 200
< Date: Mon, 04 Mar 2013 05:13:54 GMT
< Server: Apache/2.2.15 (Red Hat)
< X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.17
< X-OpenShift-Identity: qgong+1(a)redhat.com
< X-OAuth-Scopes: session
< X-UA-Compatible: IE=Edge
< ETag: "7ccc1fa5dc458dd7c96aad299de6d3ea"
< Cache-Control: max-age=0, private, must-revalidate
< X-Request-Id: 6e664d41d3b15a951d6a96066326fc11
< X-Runtime: 10.374310
< X-Rack-Cache: invalidate, pass
< Status: 200
< Content-Length: 11047
< Content-Type: application/xml; charset=utf-8
< Vary: Accept-Encoding,User-Agent
< Strict-Transport-Security: max-age=15768000
< ProxyTime: D=11017145
<
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<type>domain</type>
<data>
<domain>
<id>honkabonka</id>
<suffix>dev.rhcloud.com</suffix>
<links>
<link>
<rel>Get domain</rel>
<method>GET</method>
<href>https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/hon...</href>
<required-params/>
<optional-params/>
</link>
<link>
<rel>List applications</rel>
<method>GET</method>
<href>https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/hon...</href>
<required-params/>
<optional-params/>
</link>
<link>
<rel>Create new application</rel>
<method>POST</method>
<href>https://ec2-23-22-110-226.compute-1.amazonaws.com/broker/rest/domains/hon...</href>
<required-params>
<param>
<name>name</name>
<type>string</type>
<description>Name of the application</description>
<valid-options/>
....
> Error when renaming a domain with 1+ applications
> -------------------------------------------------
>
> Key: JBIDE-13666
> URL: https://issues.jboss.org/browse/JBIDE-13666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: rename-domain-error.png
>
>
> This is a TRACKER/WATCHER issue that helps us tracking the fixing-progress on OpenShift (https://bugzilla.redhat.com/show_bug.cgi?id=916330). There's nothing we can do about this.
> When trying to rename an existing domain to a domain name which already exists (within different openshift account):
> {code}
> Could not rename domain "sbunciak": [Operation failed with exit code "1".Reason given: "
> Problem:
> Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa.
> Summary:
> When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa.
> Resolution:
> Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples."]
> Could not request https://openshift.redhat.com/broker/rest/domains/pipistik: Operation failed with exit code "1".Reason given: "
> Problem:
> Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa.
> Summary:
> When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa.
> Resolution:
> Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples."
> {code}
> This message really doesn't describe the real problem - that I'm trying to use a domain name which is already used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBIDE-13666) Error when renaming a domain with 1+ applications
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13666?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13666:
-------------------------------------------------
qgong(a)redhat.com <qgong(a)redhat.com> changed the Status of [bug 916330|https://bugzilla.redhat.com/show_bug.cgi?id=916330] from ON_QA to VERIFIED
> Error when renaming a domain with 1+ applications
> -------------------------------------------------
>
> Key: JBIDE-13666
> URL: https://issues.jboss.org/browse/JBIDE-13666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: rename-domain-error.png
>
>
> This is a TRACKER/WATCHER issue that helps us tracking the fixing-progress on OpenShift (https://bugzilla.redhat.com/show_bug.cgi?id=916330). There's nothing we can do about this.
> When trying to rename an existing domain to a domain name which already exists (within different openshift account):
> {code}
> Could not rename domain "sbunciak": [Operation failed with exit code "1".Reason given: "
> Problem:
> Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa.
> Summary:
> When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa.
> Resolution:
> Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples."]
> Could not request https://openshift.redhat.com/broker/rest/domains/pipistik: Operation failed with exit code "1".Reason given: "
> Problem:
> Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa.
> Summary:
> When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa.
> Resolution:
> Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples."
> {code}
> This message really doesn't describe the real problem - that I'm trying to use a domain name which is already used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2456 at 3/3/13 11:52 PM:
-----------------------------------------------------------
[~nickboldt]:
The link you gave no longer worked, presumably because I left it so long before coming back to the JIRA (sorry!) and the builds are marching forwards.
Instead I tried building the current source zip, so
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr...
and ran into errors (however I think these might be unconnected to the izPack issue):
{code}
[ERROR] Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 requires 'com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT depends on: org.jboss.tools.maven.gwt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
{code}
Actually, this is caused by changing the baseline version of GWT in the Extras/Central site from 3.1 to 3.2, as in JBDS-2486.
was (Author: mmurray):
[~nickboldt]:
The link you gave no longer worked, presumably because I left it so long before coming back to the JIRA (sorry!) and the builds are marching forwards.
Instead I tried building the current source zip, so
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr...
and ran into errors (however I think these might be unconnected to the izPack issue):
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.apache.axis-1.4.0.v201005080400.jar/lib can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.5 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.6 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.jboss.tools.forge.runtime.ext-1.2.0.Alpha1-v20130227-0639-B24.jar/bin can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[INFO] Computing target platform for MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Resolving dependencies of MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Cannot complete the request. Generating details.
[INFO] Cannot complete the request. Generating details.
[INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 requires 'com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT depends on: org.jboss.tools.maven.gwt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77)
at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354)
at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more
> JBDS should be buildable from source zip (or at least document the limitations)
> -------------------------------------------------------------------------------
>
> Key: JBDS-2456
> URL: https://issues.jboss.org/browse/JBDS-2456
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 7.0.0.Alpha2
>
>
> As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing:
> {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote}
> It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either).
> Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2456:
---------------------------------------
[~nickboldt]:
The link you gave no longer worked, presumably because I left it so long before coming back to the JIRA (sorry!) and the builds are marching forwards.
Instead I tried building the current source zip, so
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_tr...
and ran into errors (however I think these might be unconnected to the izPack issue):
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.apache.axis-1.4.0.v201005080400.jar/lib can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.5 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.eclipse.mylyn.discovery.ui-3.9.0.I20130205-1655.jar/lib-e3.6 can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[WARNING] Dependency from /home/mmurray/JBDS/BuildingZIP/devstudio/product/features/com.jboss.jbds.product.feature.source to nested directory classpath entry /home/mmurray/.m2/repository/.cache/tycho/org.jboss.tools.forge.runtime.ext-1.2.0.Alpha1-v20130227-0639-B24.jar/bin can not be represented in Maven model and will not be visible to non-OSGi aware Maven plugins
[INFO] Computing target platform for MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Resolving dependencies of MavenProject: com.jboss.jbds.site:com.jboss.jbds.site.product:7.0.0-SNAPSHOT @ /home/mmurray/JBDS/BuildingZIP/devstudio/product/site/pom.xml
[INFO] Cannot complete the request. Generating details.
[INFO] Cannot complete the request. Generating details.
[INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 requires 'com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT depends on: org.jboss.tools.maven.gwt.feature.feature.group 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:170)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.maven.gwt 1.5.0.Alpha1-v20130227-2223-B13 to bundle com.google.gwt.eclipse.core 2.5.0.", "Unable to satisfy dependency from org.jboss.tools.maven.gwt.feature.feature.group 1.5.0.Alpha1-v20130227-2223-B13 to com.google.gdt.eclipse.suite.e42.feature.feature.group 3.0.1.", "No solution found because the problem is unsatisfiable."]
at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77)
at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377)
at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354)
at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:276)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:158)
... 11 more
> JBDS should be buildable from source zip (or at least document the limitations)
> -------------------------------------------------------------------------------
>
> Key: JBDS-2456
> URL: https://issues.jboss.org/browse/JBDS-2456
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 6.0.0.GA, 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Fix For: 7.0.0.Alpha2
>
>
> As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing:
> {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote}
> It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either).
> Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TOOLSDOC-251) Add documentation for Runtime detection
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-251?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-251:
------------------------------------------
I anticipate this being documented as follows:
Installation Guide:
* Install JBDS (with installer)
* Set up automatic runtime detection
Getting Started guide:
* Install JBDS (with installer)
* Set Up a Runtime Server Using Server Manager
User Guide:
* Set up automatic runtime detection
> Add documentation for Runtime detection
> ---------------------------------------
>
> Key: TOOLSDOC-251
> URL: https://issues.jboss.org/browse/TOOLSDOC-251
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Beginners Guide, Getting Started Guide
> Affects Versions: 3.2.2.Final
> Reporter: Libor Zoubek
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> Hi Isaac,
> I am going through begginers guide now (2.2.2. Adding a new application server for use with the JBoss Developer Studio). JBDS and JBoss Tools has a quite long time nice feature for adding server (and other) runtimes. I think it is a good idea to include it into guides or to switch current recommended way of adding runtimes to it - it is much more simple and it is one of many added values of JBT compared to eclipse.
> You can play with runtime detection if you open Preferences->Jboss Tools->Runtime Detection. Main idea is, that you just select any directory and JBT scans it recursively and searches for runtimes. If it founds any, you can select it to be added. Good thing is that both server runtime and server with all other runtimes (seam,jbpm) is added.
> You can contact Snjezana, she is developing runtime detectors and has much deeper details about it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months