buildbot success in ASF Buildbot on tapestry-site-production

[buildbot]

The Buildbot has detected a restored build on builder tapestry-site-production 
while building ASF Buildbot.
Full details are available at:
 http://ci.apache.org/builders/tapestry-site-production/builds/705

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: bb-cms-slave

Build Reason: The Nightly scheduler named 'tapestry-site-production' triggered 
this build
Build Source Stamp: [branch tapestry/tapestry-site] HEAD
Blamelist: 

Build succeeded!

sincerely,
 -The Buildbot




-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

buildbot failure in ASF Buildbot on tapestry-site-production

[buildbot]

The Buildbot has detected a new failure on builder tapestry-site-production 
while building ASF Buildbot.
Full details are available at:
 http://ci.apache.org/builders/tapestry-site-production/builds/704

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: bb-cms-slave

Build Reason: The Nightly scheduler named 'tapestry-site-production' triggered 
this build
Build Source Stamp: [branch tapestry/tapestry-site] HEAD
Blamelist: 

BUILD FAILED: failed compile

sincerely,
 -The Buildbot




-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: [VOTE] Drop support for Java 5 in Tapestry 5.4 (2nd attempt)

[Thiago H de Paula Figueiredo]

Thiago H. de Paula Figueiredo: +1 (binding)

Again, I only see a Java 8 T5.5 if it's a separate JAR.

--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Jenkins build is back to normal : tapestry-trunk-freestyle #1218

[Apache Jenkins Server]

See 


-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: TAP5-1213: Changes to public API

[Lance Java]

Haha... I could try / catch AbstractMethodError and get rid of Binding2 /
PropertyConduit2. Win!

Jokes...
 On 20 May 2014 17:46, "Jochen Kemnade"  wrote:

> True, but if they occur, the cause is not so easy to find IMO.
>

Re: TAP5-1213: Changes to public API

[Jochen Kemnade]

True, but if they occur, the cause is not so easy to find IMO.

Re: Issues with bulk-close-candidate label

[Jochen Kemnade]

I'll do it once beta 6 is publicly available, then people can check their
issues against that.

Re: [VOTE] Drop support for Java 5 in Tapestry 5.4 (2nd attempt)

[Kalle Korhonen]

Can other PMC members please weigh in here. Jochen, no reason to close the
vote till you have a binding majority decision either way.

Kalle


On Mon, May 19, 2014 at 6:11 AM, Kristian Marinkovic <
kristian.marinko...@gmail.com> wrote:

> Kristian Mairnkovic: +1 (non-binding)
>
> i don't see any reason not to raise the minimun requirement to 1.6. i've to
> admit most of my Tapestry apps run on Java 1.6. anyways.
>
>
> On Mon, May 19, 2014 at 1:54 PM, Bob Harner  wrote:
>
> > Bob Harner: +1 (non-binding)
> > On May 18, 2014 1:05 PM, "Jochen Kemnade"  wrote:
> >
> > > There have been discussions whether we want to keep compatibility with
> > > Java 5 for the upcoming 5.4 release.
> > > Java 5 is EOSL since October 2009.
> > > While requiring Java 6 would not bring us much benefits, there might be
> > > some libraries that we cannot use because they do not support Java 5.
> > > Also, we'd spare ourselves some efforts not having to support Java 5
> > > anymore.
> > > The vote will run for 3 days and, if it succeeds, I will increase the
> > > minimum required Java version to 1.6.
> > >
> > > Jochen Kemnade: +1 (non-binding)
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> > > For additional commands, e-mail: dev-h...@tapestry.apache.org
> > >
> > >
> > >
> >
>

Re: TAP5-1213: Changes to public API

[Lance Java]

I was referring to the exception being rare, not third party
implementations.

Keep in mind that the exception will only occur when invoking the new
method on ComponentResources. At the moment there is no such code in
existence.
 On 20 May 2014 13:51, "Thiago H de Paula Figueiredo" 
wrote:

> On Tue, 20 May 2014 07:20:21 -0300, Lance Java 
> wrote:
>
>  This would only occur in third party bindings / propertyConduits that
>> don't extend core (internal) implementations.
>>
>> IMHO these exceptions are likely to be rare as hen's teeth ;)
>>
>
> Agreed for ComponentResources, less agreed for Binding and disagreed for
> PropertyConduit, which is used inside some projects to implement some
> properties for BeanModel-based components. This is *not* uncommon to be
> found in non-library code.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
>

buildbot success in ASF Buildbot on tapestry-site-production

[buildbot]

The Buildbot has detected a restored build on builder tapestry-site-production 
while building ASF Buildbot.
Full details are available at:
 http://ci.apache.org/builders/tapestry-site-production/builds/691

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: bb-cms-slave

Build Reason: The Nightly scheduler named 'tapestry-site-production' triggered 
this build
Build Source Stamp: [branch tapestry/tapestry-site] HEAD
Blamelist: 

Build succeeded!

sincerely,
 -The Buildbot




-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

buildbot failure in ASF Buildbot on tapestry-site-production

[buildbot]

The Buildbot has detected a new failure on builder tapestry-site-production 
while building ASF Buildbot.
Full details are available at:
 http://ci.apache.org/builders/tapestry-site-production/builds/690

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: bb-cms-slave

Build Reason: The Nightly scheduler named 'tapestry-site-production' triggered 
this build
Build Source Stamp: [branch tapestry/tapestry-site] HEAD
Blamelist: 

BUILD FAILED: failed compile

sincerely,
 -The Buildbot




-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: [VOTE] Tapestry 5.4-beta-6

[Thiago H de Paula Figueiredo]

Thiago H. de Paula Figueiredo: +1 (binding)

--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: TAP5-1213: Changes to public API

[Thiago H de Paula Figueiredo]

On Tue, 20 May 2014 07:20:21 -0300, Lance Java   
wrote:


This would only occur in third party bindings / propertyConduits that  
don't extend core (internal) implementations.


IMHO these exceptions are likely to be rare as hen's teeth ;)


Agreed for ComponentResources, less agreed for Binding and disagreed for  
PropertyConduit, which is used inside some projects to implement some  
properties for BeanModel-based components. This is *not* uncommon to be  
found in non-library code.


--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br

-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: TAP5-1213: Changes to public API

[Michael Wyraz]

In this instance, I would assume an AbstractMethodError would be 
thrown when calling the new method: 
ComponentResources.getBoundGenericType(paramName) This would only 
occur in third party bindings / propertyConduits that don't extend 
core (internal) implementations. IMHO these exceptions are likely to 
be rare as hen's teeth ;) 
And the exception would only be thrown if the new method is called (e.g. 
via ComponentResources) which is only the case for new code. So a 
problem occurs only if new code uses old bindings. Old code that uses 
old bindings would still work without problems. If I have a voice, I 
vote for API change in this cases. This is better to have Binding2, 
Binding2, BindingN (imagine what once would happen if some binding 
implements Binding 1,2,4 but not 3 ;-) ).


Do you think the feature could make it in the new beta?

Kind Regards,
Michael.


--

Mit freundlichen Grüßen / Regards

Michael Wyraz

evermind GmbH
Schorlemmerstraße 1
04155 Leipzig

Tel.:   +49 (0)341-25 39 66 - 0
Fax:+49 (0)341-25 39 66 - 1
Funk:   +49 (0)177-73 00 00 3
E-Mail: michael.wy...@evermind.de

HRB: 21586
Amtsgericht Leipzig

Geschäftsführer:
Christoph Klemm
Thomas Grünert
Michael Wyraz


-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Re: TAP5-1213: Changes to public API

[Lance Java]

> wouldn't adding methods to the existing interfaces lead to libraries
written for (and compiled against) Tapestry 5.3 would not work with
Tapestry 5.4 anymore?

In this instance, I would assume an AbstractMethodError would be thrown
when calling the new method:
ComponentResources.getBoundGenericType(paramName)

This would only occur in third party bindings / propertyConduits that don't
extend core (internal) implementations.

IMHO these exceptions are likely to be rare as hen's teeth ;)

Re: [VOTE] Tapestry 5.4-beta-6

[Howard Lewis Ship]

Having trouble getting network access at night to perform the final release
step, so I'm just letting the vote continue.

I'm at a client site all day this week.


On Mon, May 19, 2014 at 12:55 PM, Bob Harner  wrote:

> Bob Harner: +1 (non-binding)
> On May 18, 2014 10:10 AM, "Taha Siddiqi"  wrote:
>
> > Taha Hafeez: +1 (non-binding)
> >
> > On May 18, 2014, at 5:08 PM, Kristian Marinkovic wrote:
> >
> > > Kristian Marinkovic: +1 (non-binding)
> > >
> > >
> > > On Sat, May 17, 2014 at 10:48 AM, françois facon  > >wrote:
> > >
> > >> François Facon: +1 (non-binding)
> > >>
> > >>
> > >> 2014-05-15 23:39 GMT+02:00 Howard Lewis Ship :
> > >>
> > >>> I've created and uploaded a release of Tapestry 5.4-beta-6, ready to
> be
> > >>> voted upon.
> > >>>
> > >>> The source and source downloads are uploaded to:
> > >>>
> > >>> http://people.apache.org/~hlship/tapestry-releases/
> > >>>
> > >>> and the Maven artifacts staged to:
> > >>>
> > >>>
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-1014
> > >>>
> > >>> Please examine these files to determine if the new release,
> 5.4-beta-6,
> > >> is
> > >>> ready.
> > >>>
> > >>> I've also created a 5.4-beta-6 tag in Git:
> > >>>
> > >>>
> > >>>
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;a=commit;h=c5600a8de7645fb7bd5cc21b38f8902a36c1b840
> > >>>
> > >>> Vote will run for three days; On a successful vote, I'll release the
> > >> Maven
> > >>> artifacts, and move the source and javadoc distributions from these
> > >>> directories
> > >>> to the proper distribution directories and update the Tapestry site
> > >>> documentation, and send out appropriate notifications.
> > >>>
> > >>>
> > >>> Howard M. Lewis Ship: +1 (binding)
> > >>>
> > >>> --
> > >>> Howard M. Lewis Ship
> > >>>
> > >>> Creator of Apache Tapestry
> > >>>
> > >>> The source for Tapestry training, mentoring and support. Contact me
> to
> > >>> learn how I can get you up and productive in Tapestry fast!
> > >>>
> > >>> (971) 678-5210
> > >>> http://howardlewisship.com
> > >>> @hlship
> > >>>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: dev-h...@tapestry.apache.org
> >
> >
>



-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com
@hlship

Re: TAP5-1213: Changes to public API

[Jochen Kemnade]

Am 20.05.2014 08:23, schrieb Lance Java:

I agree but thought I was in the minority.

The extra interfaces have increased the complexity and require third
parties to know about the nuances of the implementation. Adding methods to
the public API may cause compilation errors (in rare cases) but at least
it's clear.

Anyone else have an opinion?


Unfortunately, I haven't had the chance to look at the changes too 
closely yet, so I'm not sure if this is relevant at all. But wouldn't 
adding methods to the existing interfaces lead to libraries written for 
(and compiled against) Tapestry 5.3 would not work with Tapestry 5.4 
anymore?


Jochen

-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org

Build failed in Jenkins: tapestry-trunk-freestyle #1217

[Apache Jenkins Server]

See 

Changes:

[jkemnade] TAP5-2266: extend support for HTML content inside parameter JavaDoc

[jkemnade] fix some typos

[jkemnade] TAP5-2333: only query System.nanoTime() if we're going to use the 
result

[jkemnade] avoid more System.nanoTime() calls if we're not going to use the 
results

[uklance] TAP5-1213 - Access generic type for bound parameters

[uklance] TAP5-1213 - Refactor public API changes to be backwards compatible

--
[...truncated 28628 lines...]
   BeanBlockOverrideSource: DEFINED
   BeanBlockSource: DEFINED
   BeanModelSource: DEFINED
 BindingSource: DEFINED
  ChainBuilder: VIRTUAL
  ClassNameLocator: REAL
ClasspathAssetAliasManager: DEFINED
 ClasspathAssetFactory: DEFINED
  ClasspathScanner: REAL
 ClasspathURLConverter: REAL
 ClientBehaviorSupport: DEFINED
 ClientDataEncoder: DEFINED
  ClientPersistentFieldStorage: DEFINED
 ClientPersistentFieldStrategy: DEFINED
   ClientWhitelist: DEFINED
 Compatibility: DEFINED
   ComponentClassCache: DEFINED
ComponentClassResolver: REAL
 ComponentClassTransformWorker: DEFINED
  ComponentClassesInvalidationEventHub: REAL
  ComponentDefaultProvider: DEFINED
 ComponentEventLinkEncoder: DEFINED
 ComponentEventLinkTransformer: DEFINED
  ComponentEventRequestHandler: DEFINED
 ComponentEventResultProcessor: DEFINED
  ComponentInstanceResultProcessor: DEFINED
   ComponentInstantiatorSource: DEFINED
 ComponentMessagesInvalidationEventHub: DEFINED
   ComponentMessagesSource: DEFINED
  ComponentModelSource: DEFINED
   ComponentPageElementResourcesSource: DEFINED
 ComponentProxyFactory: DEFINED
   ComponentRequestHandler: DEFINED
  ComponentRequestSelectorAnalyzer: DEFINED
  ComponentResourceLocator: DEFINED
   ComponentSource: DEFINED
  ComponentTemplateLocator: DEFINED
   ComponentTemplateSource: DEFINED
ComponentTemplatesInvalidationEventHub: DEFINED
   CompressionAnalyzer: DEFINED
   ContentTypeAnalyzer: DEFINED
   Context: DEFINED
   ContextAssetFactory: DEFINED
 ContextBindingFactory: DEFINED
ContextPathEncoder: DEFINED
   ContextValueEncoder: DEFINED
CookieSink: DEFINED
  CookieSource: DEFINED
   Cookies: DEFINED
   CoreJavaScriptStack: DEFINED
  DashboardManager: DEFINED
  DataTypeAnalyzer: DEFINED
 DateUtilities: DEFINED
   DefaultDataTypeAnalyzer: DEFINED
  DefaultImplementationBuilder: VIRTUAL
 DeferredExecution: DEFINED
DeprecationWarning: DEFINED
 DynamicTemplateParser: VIRTUAL
  EndOfRequestEventHub: REAL
   Environment: DEFINED
EnvironmentalShadowBuilder: VIRTUAL
 ExceptionAnalyzer: DEFINED
  ExceptionTracker: DEFINED
   FactoryDefaults: REAL
 FieldTranslatorSource: DEFINED
FieldValidationSupport: DEFINED
   FieldValidatorDefaultSource: DEFINED
  FieldValidatorSource: DEFINED
   FormSupport: DEFINED
 Heartbeat: DEFINED
  HiddenFieldLocationRules: DEFINED
HttpServletRequest: DEFINED
 HttpServletRequestHandler: VIRTUAL
   HttpServletResponse: DEFINED
IgnoredPathsFilter: DEFINED
 InjectionProvider: DEFINED
 InternalComponentInvalidationEventHub: REAL
InternalRequestGlobals: DEFINED
  JavaScriptStackAssembler: DEFINED
JavaScriptStackPathConstructor: DEFINED
 JavaScriptStackSource: DEFINED
 JavaScriptSupport: DEFINED
   LazyAdvisor: DEFINED
   LinkCreationHub: DEFINED
LinkSource: DEFINED

Re: tapestry-ioc & java 8

[Lance Java]

Tapestry has switched to plastic for its byte code magic. Currently,
plastic isn't well documented. I find that the best documentation currently
is the test cases. Perhaps you can find your answer here:

https://github.com/apache/tapestry-5/tree/master/plastic/src/test/groovy/org/apache/tapestry5/plastic
 On 19 May 2014 23:46, "Jigar Joshi"  wrote:

> Hello
>
> ​with tapestry 5.3.4 and java 7 with use of
> org.apache.tapestry5.ioc.services.ClassFactory
>
>
>
> private Class createProxyClass(ServiceResources resources) {
> Class serviceInterface = resources.getServiceInterface();
>
> ClassFab cf = classFactory.newClass(serviceInterface);
>
> // add field
> cf.addField("_creator", Modifier.PRIVATE | Modifier.FINAL,
> SomeClass.class);
>
> // Constructor takes a ServiceCreator
> cf.addConstructor(new Class[] { SomeClass.class }, null, "_creator
> = $1;");
>
> // add method
> String body = format("return (%s) _creator.get();",
> serviceInterface.getName());
> MethodSignature sig = new MethodSignature(serviceInterface,
> SCOPE_METHOD_NAME, null, null);
> cf.addMethod(Modifier.PRIVATE, sig, body);
> String toString = format("",
> scope, resources.getServiceId(),
> serviceInterface.getName());
>
> cf.proxyMethodsToDelegate(serviceInterface, SCOPE_METHOD_NAME +
> "()", toString);
>
> return cf.createClass();
> }
>
>
>
>
>
> with tapestry 5.4-beta3 this class has been removed (it was depricated)
>
> I played around a little bit to find related implementation in new replaced
> class
>
> org.apache.tapestry5.ioc.services.PlasticProxyFactory
>
> couldn't find it offhand, how to achieve same thing with tapestry 5.4 ?
>
> Thanks!
> Jigar
>