[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ]
Snjezana Peco commented on JBDS-2956:
-------------------------------------
If JBDS 7 includes the javax.xml.ws and javax.xml.bind plugin, the issue is caused by OSGi changes in Luna.
> Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2956
> URL: https://issues.jboss.org/browse/JBDS-2956
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 8.0.0.Alpha2
> Environment: 64-bit Fedora 17
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, spring_projects.png
>
>
> After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue.
> See attached file.
--
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, 3 months
[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ]
Marián Labuda commented on JBDS-2956:
-------------------------------------
Yeah, but why this is not happening in JBDS 7.1.x? Only in JBDS 8? I use JDK 7 all the time. And JBDS 7 use same version of Spring IDE as this one.
> Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2956
> URL: https://issues.jboss.org/browse/JBDS-2956
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 8.0.0.Alpha2
> Environment: 64-bit Fedora 17
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, spring_projects.png
>
>
> After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue.
> See attached file.
--
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, 3 months
[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2956:
-------------------------------------------
[~mlabuda] can you verify this issue also occurs on older JBDS versions like JBDS 6 and 7 ? (I assume it would based on [~snjeza] s explanation)
> Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2956
> URL: https://issues.jboss.org/browse/JBDS-2956
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 8.0.0.Alpha2
> Environment: 64-bit Fedora 17
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, spring_projects.png
>
>
> After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue.
> See attached file.
--
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, 3 months
[JBoss JIRA] (JBIDE-15476) Allow users to provide downloadable cartidges
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15476?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15476:
--------------------------------
Summary: Allow users to provide downloadable cartidges (was: Allow users to provide downloadble cartidges)
> Allow users to provide downloadable cartidges
> ---------------------------------------------
>
> Key: JBIDE-15476
> URL: https://issues.jboss.org/browse/JBIDE-15476
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: help_wanted
> Fix For: 4.2.0.Beta1
>
> Attachments: 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.png, add-cartridge.png, add-downloadable-cartridge.png, crobson_2014-01-28 16.11.png, new-application-1.png, new-application-2.png
>
>
> OpenShift allows lately to provide your very own cartridge by giving it a git-url where the cartridge source may get cloned from. In the Web-UI this looks as follows:
> !add-downloadable-cartridge.png!
--
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, 3 months
[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ]
Snjezana Peco commented on JBDS-2956:
-------------------------------------
The issue happens because Spring IDE (the org.springframework.web plugin) exports some javax.xml.* packages.
I suppose Spring does it in order they to be compatible with JDK 5.
Your JBT distribution doesn't include the javax.xml.ws and javax.xml.bind plugin. That's why you can't reproduce the issue in JBT.
JBDS includes these two plugins. JDK 6/7 already contains the javax.xml.ws and javax.xml.bind package and OSGi can't solve the org.springframework.web plugin because there are two chains for those packages.
A workaround: remove the javax.xml.ws and javax.xml.bind plugin from JBDS/JBT.
> Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"
> --------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2956
> URL: https://issues.jboss.org/browse/JBDS-2956
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 8.0.0.Alpha2
> Environment: 64-bit Fedora 17
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, spring_projects.png
>
>
> After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue.
> See attached file.
--
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, 3 months
[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs especially during startup
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15932:
---------------------------------------------
just to be precise, as long as there is no way to disable the show on output option we can't have it default to show up since it gets annoying it shows up blocking access to other views.
> CordovaSim needs to display console logs especially during startup
> ------------------------------------------------------------------
>
> Key: JBIDE-15932
> URL: https://issues.jboss.org/browse/JBIDE-15932
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.1.Beta1
> Reporter: Gorkem Ercan
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: jbds711
> Fix For: 4.1.2.CR1
>
>
> When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console so the user can be notified about errors happening early on.
> Just using firebug or similar would not solve this issue since it is not started early enough.
--
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, 3 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15482:
---------------------------------------------
[~dgolovin] sorry to be dense but what do you mean here ? That you are missing that we have an updatesite that is a composite of the last 2-3 builds at lest ?
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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, 3 months
[JBoss JIRA] (JBIDE-16734) JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16734?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-16734:
----------------------------------
Description:
JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields.
Eg:
{code}
@Path("resource")
@Singleton
public static class MySingletonResource {
@QueryParam("query")
String param; // WRONG: initialization of application will fail as you cannot
// inject request specific parameters into a singleton resource.
@GET
public String get() {
return "query param: " + param;
}
}
{code}
The exception exists for specific request objects which can injected even into constructor or class fields. For these objects the runtime will inject proxies which are able to simultaneously server more request. These request objects are HttpHeaders, Request, UriInfo, SecurityContext. These proxies can be injected using the @Context annotation
was:
JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields.
Eg:
{code}
@Path("resource")
@Singleton
public static class MySingletonResource {
@QueryParam("query")
String param; // WRONG: initialization of application will fail as you cannot
// inject request specific parameters into a singleton resource.
@GET
public String get() {
return "query param: " + param;
}
}
{code}
> JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16734
> URL: https://issues.jboss.org/browse/JBIDE-16734
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.1.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.x
>
>
> JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields.
> Eg:
> {code}
> @Path("resource")
> @Singleton
> public static class MySingletonResource {
>
> @QueryParam("query")
> String param; // WRONG: initialization of application will fail as you cannot
> // inject request specific parameters into a singleton resource.
>
> @GET
> public String get() {
> return "query param: " + param;
> }
> }
> {code}
> The exception exists for specific request objects which can injected even into constructor or class fields. For these objects the runtime will inject proxies which are able to simultaneously server more request. These request objects are HttpHeaders, Request, UriInfo, SecurityContext. These proxies can be injected using the @Context annotation
--
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, 3 months
[JBoss JIRA] (JBIDE-16720) Allow easier access to openshift operations from jboss servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16720:
-------------------------------------
Comment: was deleted
(was: Not fully sure if the following is correct:
{quote}
Unfortunately there is currently no obvious distinction for a user between #1 and #2.
{quote}
In openshift-java-client you can ask an ICartrdige#isDownloadable (which is available for IStandaloneCartridge and IEmbeddedCartridge) which will return *true* in case the cartridge has a valid url (which is not the case for built-ins).
https://github.com/openshift/openshift-java-client/blob/master/src/main/j...
https://github.com/openshift/openshift-java-client/blob/master/src/main/j...
{code}
@Override
public boolean isDownloadable() {
return url != null;
}
{code}
What do I miss?)
> Allow easier access to openshift operations from jboss servers
> --------------------------------------------------------------
>
> Key: JBIDE-16720
> URL: https://issues.jboss.org/browse/JBIDE-16720
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.1.Final
> Reporter: Mark Drilling
>
> We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case.
> Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push.
> Currently, we connect to an OpenShift DV instance like this:
> 1) Deploy DV cartridge via OpenShift web console.
> 2) Port forward from command line using rhc port-forward
> 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective
> The issues we observed:
> 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo.
> 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list.
> Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.)
--
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, 3 months
[JBoss JIRA] (JBIDE-16734) JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-16734:
-------------------------------------
Summary: JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields
Key: JBIDE-16734
URL: https://issues.jboss.org/browse/JBIDE-16734
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: webservices
Affects Versions: 4.1.1.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.x
JAX-RS Validation: should report an error when resource is annotated with @javax.inject.Singleton and has JAX-RS fields.
Eg:
{code}
@Path("resource")
@Singleton
public static class MySingletonResource {
@QueryParam("query")
String param; // WRONG: initialization of application will fail as you cannot
// inject request specific parameters into a singleton resource.
@GET
public String get() {
return "query param: " + param;
}
}
{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, 3 months