[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13671:
-------------------------------------
Will this ignore changes to the version files? For example, if a plugin or module has 0 code changes, 0 plugin changes, 0 resource changes, EXCEPT for a change to the version, what timestamp will be used?
Further question: If it ignores changes to the version string, and it has a matching build stamp to the previous release, and there are 0 code changes, couldn't we just use the previously released version?
> parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
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
13 years, 1 month
[JBoss JIRA] (JBDS-2487) default EAP startup parameters unusable
by Aleksandar Kostadinov (JIRA)
Aleksandar Kostadinov created JBDS-2487:
-------------------------------------------
Summary: default EAP startup parameters unusable
Key: JBDS-2487
URL: https://issues.jboss.org/browse/JBDS-2487
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: servers
Affects Versions: 6.0.0.GA
Environment: all
Reporter: Aleksandar Kostadinov
Default parameters to start JBoss AS server/EAP are not in sync with standalone.conf
We have as default in JBDS: -Xmx512m -XX:MaxPermSize=256m
While in standalone.conf we have defaults: -Xms1303m -Xmx1303m -XX:MaxPermSize=256m
The server starts but trying to deploy a simple web application causes server to OOM. Additionally finding where to change server parameters in JBDS is non-intuitive. It was hard to spot the button even after seeing the correct instructions how to do so.
Other users have also hit this issue [1].
FYI I've used the standalone JBDS 6.0.0 binary + a separate EAP 6.0.1 installation if that matters for configuration options.
[1] http://stackoverflow.com/questions/880255/out-of-memory-error-starting-jb...
--
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
13 years, 1 month