[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:
---------------------------------------------
No, I just think changing url schemes are unnecessary and if you want to spot differences then make a difference in the content no the url.
> 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: Nick Boldt
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Martes Wigglesworth (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Martes Wigglesworth updated JBIDE-15597:
----------------------------------------
Attachment: jira-JBIDE-15598-wizard-screenshot.jpeg
Default buttons wizard view
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, jira-JBIDE-15598-wizard-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
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, 6 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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15482:
------------------------------------
[~maxandersen] I don't understand what you mean. Permanent file? These are FOLDERS of many files, not just a single file. Where would you put this file? Are you talking about sticking an update site zip in Nexus again? Remember, the update site zip is only PART of what's housed in a build folder - we have a lot of metadata associated w/ each update site build, too.
[~mmalina]: If you need a static URL for "the latest build's update site", that's being generated. For example,
http://download.jboss.org/jbosstools/builds/staging/CI/jbosstools-birt_ma...
http://download.jboss.org/jbosstools/builds/staging/CI/jbosstools-liverel...
_Note that content is not yet up to date - I just copied stuff over for testing._
If you need a static URL for "the latest build folder w/ metadata" (eg., logs, git rev, etc.) I can provide that -- it's not being generated right now so you'd have to browse for the correct subfolder each time.
> 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: Nick Boldt
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-11975) JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11975?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-11975:
------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11975
> URL: https://issues.jboss.org/browse/JBIDE-11975
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Reporter: Vimal Kansal
> Assignee: Koen Aers
> Labels: jpa
> Fix For: 4.2.x
>
>
> Hi,
> I am using JBDS 5.0 Beta 3. I created a POJO with follwoing attributes :
> String username;
> String password
> String loginCount;
> Then I invoked conetxt menu option "Generate Hibernate/JPA annotations", it generates only @Entity annotation. Obviously there is no way for the wizard to find out which attribute should act as PK. However if I include a string "id" anywhere in "username" e.g idusername, usernameid, useridname, it assumes it to be the PK and generates @Id and @GeneratedValue annotation. I wonder if this is by design? I think a better approach would be to let the user choose on the wizard, which field he wants to mark as PK.
--
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, 6 months
[JBoss JIRA] (JBIDE-11975) JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11975?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-11975:
-----------------------------------
Moving to the 4.2.x stream as 4.1.x is feature frozen
> JPA Tooling - Adding JPA Annotations to a POJO - Allow users to choose the field to be marked as PK
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11975
> URL: https://issues.jboss.org/browse/JBIDE-11975
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Reporter: Vimal Kansal
> Assignee: Koen Aers
> Labels: jpa
> Fix For: 4.2.x
>
>
> Hi,
> I am using JBDS 5.0 Beta 3. I created a POJO with follwoing attributes :
> String username;
> String password
> String loginCount;
> Then I invoked conetxt menu option "Generate Hibernate/JPA annotations", it generates only @Entity annotation. Obviously there is no way for the wizard to find out which attribute should act as PK. However if I include a string "id" anywhere in "username" e.g idusername, usernameid, useridname, it assumes it to be the PK and generates @Id and @GeneratedValue annotation. I wonder if this is by design? I think a better approach would be to let the user choose on the wizard, which field he wants to mark as PK.
--
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, 6 months
[JBoss JIRA] (JBIDE-13855) Invalid JPA Error message for Hibernate Joined inheritance
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13855?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-13855:
------------------------------------
I had set this error to ignore previously and now after enabling it in 4.1 the warning does not appear to be resurfacing.
Looks like it may have been fixed between 4.0 and 4.1
> Invalid JPA Error message for Hibernate Joined inheritance
> ----------------------------------------------------------
>
> Key: JBIDE-13855
> URL: https://issues.jboss.org/browse/JBIDE-13855
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.0.0.Final
> Reporter: Cody Lerum
> Assignee: Koen Aers
> Fix For: 4.1.x
>
>
> Discriminator column "DTYPE" cannot be resolved on table "Order_"
> In this case
> {code}
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @Table(name = "Order_")
> public abstract class Order implements Serializable
> {code}
> Hibernate does not require the use of a Discriminator column
--
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, 6 months
[JBoss JIRA] (JBIDE-15577) Hibernate Console problem while creating session factory
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15577?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-15577:
-----------------------------------
Hi Guillaume,
I have succesfully imported your project into a workspace using JBoss Tools 4.1.0.Final. I see that this sample project is depending on Tomcat 6.0 and is using MySQL. Can you provide me with a detailed setup and step by step instructions so that I can try to reproduce your issue?
Cheers,
Koen
> Hibernate Console problem while creating session factory
> --------------------------------------------------------
>
> Key: JBIDE-15577
> URL: https://issues.jboss.org/browse/JBIDE-15577
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.x
> Environment: Eclipse 4.3 (kepler), hibernate tools 3.7.0, Hibernate 4.2.2, jdk1.6.0.38
> Reporter: Guillaume JOUVELOT
> Assignee: Koen Aers
> Fix For: 4.2.x
>
>
> When I try to use hibernate console in order to test HQL queries I've the following error message from eclipse :
> {color:red}java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;{color}
> And the eclipse log file :
> !ENTRY org.hibernate.eclipse.console 4 4 2013-09-27 15:57:20.198
> !MESSAGE Problems while creating sessionfactory
> !SUBENTRY 1 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198
> !MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> !STACK 0
> java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance0(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84)
> at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383)
> at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273)
> at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> !SUBENTRY 2 org.hibernate.eclipse.console 4 150 2013-09-27 15:57:20.198
> !MESSAGE java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> !STACK 0
> java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object;
> at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.<clinit>(C3P0ConnectionProvider.java:58)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at java.lang.Class.newInstance0(Unknown Source)
> at java.lang.Class.newInstance(Unknown Source)
> at org.hibernate.connection.ConnectionProviderFactory.initializeConnectionProviderFromConfig(ConnectionProviderFactory.java:174)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:102)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84)
> at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:438)
> at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91)
> at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2163)
> at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2159)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1383)
> at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:278)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:107)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:273)
> at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> I've well configured my session factory.
--
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, 6 months
[JBoss JIRA] (JBIDE-15651) EAP 6.2 cannot be connected to in MBean Explorer
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15651?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15651:
---------------------------------------
I tried this even after applying the fix in JBIDE-15614 but that didn't help.
BTW, [~rob.stryker] your 4.1.x branch is still on Alpha1-SNAPSHOT parent, so in order to try this fix on top of Alpha2 I had to update the parent reference first, you might want to update it - other repos have that.
> EAP 6.2 cannot be connected to in MBean Explorer
> ------------------------------------------------
>
> Key: JBIDE-15651
> URL: https://issues.jboss.org/browse/JBIDE-15651
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.1.1.Alpha2
> Environment: JBDS 7.1.0.Alpha2 B431
> Reporter: Martin Malina
> Fix For: 4.1.1.Beta1
>
>
> When you start EAP 6.2.0.ER4 (or ER5) added manually and then try Show in -> MBean Explorer, it will show the server as [disconnected] and the server won't connect.
--
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, 6 months
[JBoss JIRA] (JBIDE-15651) EAP 6.2 cannot be connected to in MBean Explorer
by Martin Malina (JIRA)
Martin Malina created JBIDE-15651:
-------------------------------------
Summary: EAP 6.2 cannot be connected to in MBean Explorer
Key: JBIDE-15651
URL: https://issues.jboss.org/browse/JBIDE-15651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.1.1.Alpha2
Environment: JBDS 7.1.0.Alpha2 B431
Reporter: Martin Malina
Fix For: 4.1.1.Beta1
When you start EAP 6.2.0.ER4 (or ER5) added manually and then try Show in -> MBean Explorer, it will show the server as [disconnected] and the server won't connect.
--
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, 6 months